[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bb5bdcf2-6bd3-49c7-b3e5-210b7f332137@lunn.ch>
Date: Mon, 19 Jan 2026 15:20:39 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Billy Tsai <billy_tsai@...eedtech.com>
Cc: Linus Walleij <linusw@...nel.org>,
Bartosz Golaszewski <brgl@...nel.org>,
Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...econstruct.com.au>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Jeffery <andrew@...id.au>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
BMC-SW <BMC-SW@...eedtech.com>
Subject: Re: [PATCH 3/5] gpio: aspeed-sgpio: Create llops to handle hardware
access
> We did consider regmap. However, llops is intended to abstract not only
> register
>
> access but also layout-specific bit mapping, which is difficult to express
>
> cleanly with a flat regmap interface.
O.K. I was just thinking, if you can swap to regmap, you could maybe
then go one step further and use gpio_regmap_register(). But if you
have extra logic in here, that will not work.
Andrew
Powered by blists - more mailing lists