[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP6Zq1iZbNnPuVnJW0=HhnOryrdZOcnNMK420H3X0KcA1k3-Uw@mail.gmail.com>
Date: Thu, 14 Dec 2023 18:50:21 +0200
From: Tomer Maimon <tmaimon77@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: pmenzel@...gen.mpg.de, Rob Herring <robh+dt@...nel.org>,
krzysztof.kozlowski+dt@...aro.org,
Conor Dooley <conor+dt@...nel.org>, avifishman70@...il.com,
tali.perry1@...il.com, Joel Stanley <joel@....id.au>,
venture@...gle.com, yuenn@...gle.com, benjaminfair@...gle.com,
Jonathan Neuschäfer <j.neuschaefer@....net>,
openbmc@...ts.ozlabs.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] soc: nuvoton: add NPCM BPC driver
Hi Arnd,
Thanks for your suggestion.
Appreciate it if Joel, OpenBMC Linux kernel maintainer, could share
his thoughts about it.
On Thu, 14 Dec 2023 at 17:49, Arnd Bergmann <arnd@...db.de> wrote:
>
> On Thu, Dec 14, 2023, at 14:09, Tomer Maimon wrote:
> > On Thu, 14 Dec 2023 at 14:44, Arnd Bergmann <arnd@...db.de> wrote:
> >> >
> >> > +config NPCM_BP
> >> > + tristate "NPCM BIOS Post Code support"
> >> > + depends on (ARCH_NPCM || COMPILE_TEST)
> >> > + help
> >> > + Provides NPCM driver to control the BIOS Post Code
> >> > + interface which allows the BMC to monitor and save
> >> > + the data written by the host to an arbitrary I/O port,
> >> > + the BPC is connected to the host thourgh LPC or eSPI bus.
> >> > +
> >>
> >> This one in particular looks like this might be implemented
> >> by more than one BMC type, it's a fairly generic functionality.
> >>
> >> Have you talked to the other maintainers of SoCs used in
> >> OpenBMC about coming up with a common interface?
> > Yes, Both Nuvoton and Aspeed use the same user-facing code to manage
> > the host snooping.
> > https://github.com/openbmc/phosphor-host-postd
>
> Ok, that's good. I found the driver in drivers/soc/aspeed/aspeed-lpc-snoop.c
> now and see that the implementation looks very similar.
>
> I think we should do two things here:
>
> - split out the common code into a shared module that exports the
> symbols to be used by either one
>
> - find a better place for both drivers outside of drivers/soc.
> I would suggest drivers/misc/bmc/ but am open to other suggestions.
>
> Arnd
Best regards,
Tomer
Powered by blists - more mailing lists