From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: arm-soc <arm@kernel.org>, arm-soc <soc@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [GIT PULL 1/2] Renesas ARM defconfig updates for v5.9
Date: Mon, 6 Jul 2020 17:40:44 +0200 [thread overview]
Message-ID: <CAK8P3a3HSRjcnmpicvAKOxnrcuZe+OVrdsiqj=eVbPKbjEcYmg@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVHXztUyvEbj6ozp-zHf5Afg_hLmf4OU8v50sF2vBmPxg@mail.gmail.com>
On Mon, Jul 6, 2020 at 4:45 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Mon, Jul 6, 2020 at 4:37 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Fri, Jul 3, 2020 at 2:07 PM Geert Uytterhoeven
> > <geert+renesas@glider.be> wrote:
> > > ----------------------------------------------------------------
> > > Renesas ARM defconfig updates for v5.9
> > >
> > > - Refresh shmobile_defconfig for v5.8-rc1
> > > - Enable additional support for Renesas platforms to
> > > shmobile_defconfig, multi_v7_defconfig, and the arm64 defconfig.
> >
> > As you write on one of the commits
> >
> > "All of the above are modular, except for Ethernet support (HDMI Audio
> > support is an optional feature of the modular ADV7511 driver)."
> >
> > I'm starting to see some demand for making more drivers loadable modules
> > that are traditionally built-in. Can you give a more specific reason why
> > this one (and I guess CONFIG_RAVB next to it) should not a loadable module?
>
> We tend to make Ethernet built-in, to ease testing using nfsroot.
> If that is no longer desirable, I guess we'll have to improve our initramfs
> skills ;-)
I'm not sure either. My feeling is that we should probably make all network
support loadable modules eventually, it seems wrong to single out yours
if your current workflow depends on the built-in driver today.
I'm pulling your branch for now, but I'll keep asking around what others
think, and we might change all drivers that can to be loadable
modules later on.
In particular, a number of chips that primarily run Android are now
changed so they can have even more fundamental drivers (pinctrl,
clk, ...) as loadable modules, and it seems like a good idea to
also support that in the defconfig.
Arnd
next prev parent reply other threads:[~2020-07-06 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 12:06 [GIT PULL 0/2] Renesas ARM SoC updates for v5.9 Geert Uytterhoeven
2020-07-03 12:06 ` [GIT PULL 1/2] Renesas ARM defconfig " Geert Uytterhoeven
2020-07-06 14:36 ` Arnd Bergmann
2020-07-06 14:45 ` Geert Uytterhoeven
2020-07-06 15:40 ` Arnd Bergmann [this message]
2020-07-06 15:48 ` Geert Uytterhoeven
2020-07-03 12:06 ` [GIT PULL 2/2] Renesas ARM DT " Geert Uytterhoeven
2020-07-06 15:51 ` [GIT PULL 0/2] Renesas ARM SoC " Arnd Bergmann
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='CAK8P3a3HSRjcnmpicvAKOxnrcuZe+OVrdsiqj=eVbPKbjEcYmg@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=soc@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).