[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aAEJPMotHxguJzC_@blossom>
Date: Thu, 17 Apr 2025 09:59:24 -0400
From: Alyssa Rosenzweig <alyssa@...enzweig.io>
To: Srinivas Kandagatla <srini@...nel.org>
Cc: fnkl.kernel@...il.com, Sven Peter <sven@...npeter.dev>,
Janne Grunau <j@...nau.net>, Neal Gompa <neal@...pa.dev>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, asahi@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Hector Martin <marcan@...can.st>
Subject: Re: [PATCH 2/3] nvmem: Add spmi-nvmem driver
> > > > +config NVMEM_SPMI
> > > > + tristate "Generic SPMI NVMEM"
> > > > + default ARCH_APPLE
> > > Why default is set to ARCH_APPLE?
> > >
> > > This will endup with y in arm64 defconfig, means increasing the size of
> > > kernel.
> >
> > I mean, eventually I think we /do/ want M1 properly supported in the
> > arm64 defconfig, no? I'm not sure what the criteria is for any other
> > driver to be defconfig or not, though.
> cat arch/arm64/configs/defconfig | grep APPLE
> CONFIG_ARCH_APPLE=y
>
> Criteria for other drivers default should be not selected,
> and should be module if they are part of defconfig, rather than
> inbuilt. Not sure how most of the ARCH_APPLE drivers ended up using
> default ARCH_APPLE.
Oh, I see what you mean, module vs in-built. Understood now, thanks for
explaining :)
Powered by blists - more mailing lists