From: Roger Quadros <rogerq@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Nishanth Menon <nm@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: make USB_DWC3 as a module instead of built-in
Date: Tue, 4 Apr 2023 14:46:11 +0300 [thread overview]
Message-ID: <076b5775-18eb-05b3-b803-c54420b3e5fe@kernel.org> (raw)
In-Reply-To: <0ffa9690-9709-669c-b44d-dbb93446ec95@linaro.org>
On 04/04/2023 13:01, Krzysztof Kozlowski wrote:
> On 04/04/2023 10:51, Arnd Bergmann wrote:
>> On Tue, Apr 4, 2023, at 10:42, Roger Quadros wrote:
>>> USB_DWC3 is not required for boot on most platforms make it
>>> as a module instead of built-in.
>>>
>>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>>> ---
>>
>> Does this save a significant amount of vmlinux size? Since this
vmlinux size reduces by ~529KB
>> is a fairly common USB driver, I think it does help to have it
>> built-in for users booting from USB_STORAGE or nfsroot over
>> USB_USBNET, which are both built-in and not uncommon.
OK.
>
> Especially that sometimes, at least for arm64 defconfig, we added as
> built-in less critical pieces (RENESAS_ETHER_SWITCH, MARVELL_10G_PHY,
> HTE_TEGRA194, SM_VIDEOCC_8250 and other non-core clock controllers).
> This change will require several systems to update their initrd to
> include USB.
OK. Please ignore this patch and the arm64 defconfig one as well. ;)
cheers,
-roger
next prev parent reply other threads:[~2023-04-04 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 8:42 Roger Quadros
2023-04-04 8:51 ` Arnd Bergmann
2023-04-04 10:01 ` Krzysztof Kozlowski
2023-04-04 11:46 ` Roger Quadros [this message]
2023-04-04 12:14 ` Arnd Bergmann
2023-04-04 12:59 ` Roger Quadros
2023-04-04 13:08 ` Arnd Bergmann
2023-04-04 15:09 ` 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=076b5775-18eb-05b3-b803-c54420b3e5fe@kernel.org \
--to=rogerq@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=arnd@arndb.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nm@ti.com \
--cc=vigneshr@ti.com \
/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
all inboxes | Powered by JetHome®