[PATCH] drivers/misc: add Aspeed LPC snoop driver

[Rick Altherr]

I expect Nuvoton to be sending upstream support for their BMC SoCs later
this year.  LPC is slowly being replaced by eSPI so, even though I expect a
few more companies to introduce BMC SoCs in the next few years, I don't
expect a huge increase in the number of LPC slave drivers.

On Tue, Jun 6, 2017 at 1:07 AM, Arnd Bergmann <arnd at arndb.de> wrote:

> On Tue, Jun 6, 2017 at 4:16 AM, Joel Stanley <joel at jms.id.au> wrote:
> > On Tue, Jun 6, 2017 at 5:16 AM, Rob Lippert <rlippert at google.com> wrote:
> >> On Sun, Jun 4, 2017 at 8:25 PM, Joel Stanley <joel at jms.id.au> wrote:
> >
> > Yeah, get_maintainers.pl only suggested lkml. cc lkml I think.
> >
> > I'm not sure if we want to put these drivers in misc, or if we want to
> > use something like drivers/soc/aspeed.
> >
> > Arnd, Greg, do you have any suggestions here?
>
> I think the main question is whether there are going to be other drivers
> like this one. Are there any other BMCs that still survive on the market
> with an LPC slave port? The only other ones I have seen were the
> old Broadcom one (apparently discontinued when Broadcom acquired
> the Emulex BMC line) and those Emulex BMCs (now part of ASpeed,
> presumably merged with the other product line) and some obscure
> Nuvoton product I could not find out much about.
>
> If we do expect more drivers like this, I'd put it into a new drivers/lpc
> directory (which we might use for both slave and master drivers,
> at least one master driver is pending merge), otherwise drivers/bus/
> or drivers/soc/ would be better.
>
> Between the last two, I'm not sure, since this still doesn't fit perfectly
> in one or the other, but both would work.
>
>         Arnd
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170606/1dae32cf/attachment.html>