From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/4] at91: Use the ddramc driver for all boards whose architecture uses it
Date: Fri, 7 Mar 2025 11:24:00 +0300 [thread overview]
Message-ID: <CAP1tNvRyshvEEEumXZEfOQr475vDsaSovYtE2xLyLJL-AirToQ@mail.gmail.com> (raw)
In-Reply-To: <Z8qrxskIpfyBO74o@pengutronix.de>
Hello.
> > diff --git a/arch/arm/mach-at91/sama5d3_devices.c b/arch/arm/mach-at91/sama5d3_devices.c
> > index f6d5617e5f..4871c2bd69 100644
> > --- a/arch/arm/mach-at91/sama5d3_devices.c
> > +++ b/arch/arm/mach-at91/sama5d3_devices.c
> > @@ -21,10 +21,9 @@
> >
> > void at91_add_device_sdram(u32 size)
> > {
> > - if (!size)
> > - size = at91sama5d3_get_ddram_size();
> > -
> > - arm_add_mem_device("ram0", SAMA5_DDRCS, size);
> > + add_generic_device("sama5-ddramc", DEVICE_ID_SINGLE, NULL,
> > + SAMA5D3_BASE_MPDDRC, SZ_512,
> > + IORESOURCE_MEM, NULL);
>
> Is this necessary? I just merged your patch that says that all SAMA5D3
> boards are merged to device tree. The device tree already has a
> "atmel,sama5d3-ddramc" node, so there shouldn't be a need to create the
> device here again.
This series was created before I realized that board files for SAMA5D3 can
be deleted completely. In general, in this case it is a patch race :)
Thanks!
next prev parent reply other threads:[~2025-03-07 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:20 [PATCH 1/4] at91:: Remove dead definition of atmel_nand_load_image() Alexander Shiyan
2025-03-05 6:20 ` [PATCH 2/4] at91: Use the ddramc driver for all boards whose architecture uses it Alexander Shiyan
2025-03-07 8:18 ` Sascha Hauer
2025-03-07 8:24 ` Alexander Shiyan [this message]
2025-03-05 6:21 ` [PATCH 3/4] at91: ddramc: Trivial code cleanup Alexander Shiyan
2025-03-05 6:21 ` [PATCH 4/4] at91: Use proper values of stashed SAMA5D2/3/4 bootsource Alexander Shiyan
2025-03-07 8:20 ` (subset) [PATCH 1/4] at91:: Remove dead definition of atmel_nand_load_image() Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP1tNvRyshvEEEumXZEfOQr475vDsaSovYtE2xLyLJL-AirToQ@mail.gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox