[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9ppGn0rLfnA3vz6@enigma.ccjz.io>
Date: Wed, 1 Feb 2023 21:28:58 +0800
From: Clay Chang <clayc@....com>
To: Andrew Jeffery <andrew@...id.au>
CC: <linux-kernel@...r.kernel.org>, <soc@...nel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <verdun@....com>,
<nick.hawkins@....com>, Arnd Bergmann <arnd@...db.de>,
"Rob Herring" <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Russell King <linux@...linux.org.uk>,
Olof Johansson <olof@...om.net>
Subject: Re: [PATCH 0/5] ARM: Add GXP SROM Support
Hi Andrew,
On Tue, Jan 31, 2023 at 09:46:42PM +0800, Clay Chang wrote:
> > I'm trying to understand whether we can find some common ground with
> > controlling e.g. Aspeed's BMCs LPC peripherals based on Arnd's query[1],
> > but the description is a bit too vague right now for me to be able to do
> > that.
> >
> > [1] https://lore.kernel.org/all/66ef9643-b47e-428d-892d-7c1cbd358a5d@app.fastmail.com/
> >
> > Andrew
I briefly studied driver/soc/aspeed/aspeed-lpc-ctrl.c, and IMO the
similarity between HPE GXP driver and Aspeed's could be that we both
expose the LPC memory addresses or registers for configuration purposes.
However, the functions to be configured could vary. There are a few sets
of registers that HPE wants to expose for configuration in the future.
So, do you think there could be some common grounds for genralization?
Please let me know if you need more information.
Thanks,
Clay
Powered by blists - more mailing lists