public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: sjg@chromium.org, u-boot@lists.denx.de, praneeth@ti.com,
	kishon@ti.com, Patrick Delaunay <patrick.delaunay@foss.st.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>
Subject: Re: [u-boot][PATCH v2 2/4] scripts: Makefile.spl: Enable memory drivers to be built for SPL
Date: Thu, 20 Oct 2022 15:23:42 +0300	[thread overview]
Message-ID: <6ac9e035-93ce-3272-13af-01fa77824d31@kernel.org> (raw)
In-Reply-To: <20221019125425.GH2020586@bill-the-cat>

Hi Tom,

On 19/10/2022 15:54, Tom Rini wrote:
> On Wed, Oct 19, 2022 at 11:17:35AM +0300, Roger Quadros wrote:
>>
>>
>> On 18/10/2022 20:40, Tom Rini wrote:
>>> On Thu, Oct 06, 2022 at 04:23:58PM +0300, Roger Quadros wrote:
>>>> We will need ti-gpmc driver for SPL. Allow memory drivers
>>>> do be built for SPL.
>>>>
>>>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>>>> ---
>>>>  scripts/Makefile.spl | 1 +
>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/scripts/Makefile.spl b/scripts/Makefile.spl
>>>> index 3bafeb4fe9..110076b22f 100644
>>>> --- a/scripts/Makefile.spl
>>>> +++ b/scripts/Makefile.spl
>>>> @@ -114,6 +114,7 @@ libs-$(CONFIG_PARTITIONS) += disk/
>>>>  endif
>>>>  
>>>>  libs-y += drivers/
>>>> +libs-y += drivers/memory/
>>>>  libs-$(CONFIG_SPL_USB_GADGET) += drivers/usb/dwc3/
>>>>  libs-$(CONFIG_SPL_USB_GADGET) += drivers/usb/cdns3/
>>>>  libs-y += dts/
>>>
>>> This ends up being the wrong approach as it then pulls in
>>> drivers/memory/stm32-fmc2-ebi.o on all of those platforms, in SPL, which
>>> is not what's intended. We need an SPL_MEMORY symbol and then gate the
>>> directory on that.
>>>

I have a question about how CONFIG_SPL_MEMORY works together with CONFIG_MEMORY.

Do we use CONFIG_SPL_MEMORY only to gate the drivers/memory directory inclusion?
Then continue to use CONFIG_MEMORY and others to enable/disable driver
build for both non-SPL and SPL case?

So drivers/memory/Makefile remains as it is?

>>
>> That's right. I'll fix it up. Will wait for your comments on the rest
>> of the series before re-spin.
> 
> Everything else is fine, I was about to merge it (with a
> %s/DM_MEMORY/MEMORY) when I saw the stm32 platforms increasing in size
> and dug in.
> 

cheers,
-roger

  reply	other threads:[~2022-10-20 12:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 13:23 [u-boot][PATCH v2 0/4] Introduce MEMORY uclass and TI GPMC driver Roger Quadros
2022-10-06 13:23 ` [u-boot][PATCH v2 1/4] dm: memory: Introduce new uclass Roger Quadros
2022-10-06 19:07   ` Simon Glass
2022-10-06 13:23 ` [u-boot][PATCH v2 2/4] scripts: Makefile.spl: Enable memory drivers to be built for SPL Roger Quadros
2022-10-18 17:40   ` Tom Rini
2022-10-19  8:17     ` Roger Quadros
2022-10-19 12:54       ` Tom Rini
2022-10-20 12:23         ` Roger Quadros [this message]
2022-10-20 12:29           ` Tom Rini
2022-10-25 23:35             ` Simon Glass
2022-10-26 10:41               ` Roger Quadros
2022-10-26 13:52                 ` Tom Rini
2022-10-26 13:53               ` Tom Rini
2022-10-06 13:23 ` [u-boot][PATCH v2 3/4] dt/bindings: memory: Add bindings for TI GPMC driver Roger Quadros
2022-10-06 13:24 ` [u-boot][PATCH v2 4/4] memory: Add " Roger Quadros

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=6ac9e035-93ce-3272-13af-01fa77824d31@kernel.org \
    --to=rogerq@kernel.org \
    --cc=kishon@ti.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=praneeth@ti.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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