From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
"Joel Stanley" <joel@jms.id.au>,
"Paul Menzel" <pmenzel@molgen.mpg.de>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Lubomir Rintel" <lkundrak@v3.sk>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Hector Martin" <marcan@marcan.st>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Sven Peter" <sven@svenpeter.dev>,
"Heiko Stuebner" <heiko@sntech.de>,
"Brian Norris" <briannorris@chromium.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] soc: nuvoton: Add SoC info driver for WPCM450
Date: Fri, 17 Jun 2022 11:28:14 +0200 [thread overview]
Message-ID: <YqxJLhkCQ2WcHdAp@latitude> (raw)
In-Reply-To: <CAK8P3a0-m1iQ2bP+dsoGTPZGMNBKqB5a6315jdgaT3tuR4WfTw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Wed, Jun 15, 2022 at 04:00:17PM +0200, Arnd Bergmann wrote:
> On Thu, Jun 9, 2022 at 11:35 PM Jonathan Neuschäfer
> <j.neuschaefer@gmx.net> wrote:
> >
> > Add a SoC information driver for Nuvoton WPCM450 SoCs. It provides
> > information such as the SoC revision.
> >
> > Usage example:
> >
> > # grep . /sys/devices/soc0/*
> > /sys/devices/soc0/family:Nuvoton NPCM
> > /sys/devices/soc0/revision:A3
> > /sys/devices/soc0/soc_id:WPCM450
> >
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> > Reviewed-by: Joel Stanley <joel@jms.id.au>
> > Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
>
> Looks good overall.
>
> > +menuconfig WPCM450_SOC
> > + bool "Nuvoton WPCM450 SoC driver"
> > + default y if ARCH_WPCM450
>
> It would be nice to make this a tristate option, as we generally
> like to keep optional drivers out of the allmodconfig vmlinux file,
> even if this is a tiny one.
Ok.
> Just add the trivial cleanup function and MODULE_LICENSE() etc tags.
The right thing to do seems to be to unregister the SoC device in the
cleanup function. Is that what you mean?
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-17 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 21:35 Jonathan Neuschäfer
2022-06-15 14:00 ` Arnd Bergmann
2022-06-17 9:28 ` Jonathan Neuschäfer [this message]
2022-06-17 11:39 ` 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=YqxJLhkCQ2WcHdAp@latitude \
--to=j.neuschaefer@gmx.net \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=conor.dooley@microchip.com \
--cc=heiko@sntech.de \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=marcan@marcan.st \
--cc=nicolas.ferre@microchip.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robert.jarzmik@free.fr \
--cc=sven@svenpeter.dev \
/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
Powered by JetHome