[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220609163920.GA7420@quicinc.com>
Date: Thu, 9 Jun 2022 09:39:20 -0700
From: Guru Das Srinagesh <quic_gurus@...cinc.com>
To: Aidan MacDonald <aidanmacdonald.0x0@...il.com>
CC: <linus.walleij@...aro.org>, <brgl@...ev.pl>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <wens@...e.org>,
<jic23@...nel.org>, <lee.jones@...aro.org>, <sre@...nel.org>,
<broonie@...nel.org>, <gregkh@...uxfoundation.org>,
<lgirdwood@...il.com>, <lars@...afoo.de>, <rafael@...nel.org>,
<linux-gpio@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-iio@...r.kernel.org>,
<linux-pm@...r.kernel.org>
Subject: Re: [PATCH v2 01/17] regmap-irq: Use sub_irq_reg() to calculate
unmask register address
On Tue, Jun 07, 2022 at 04:53:08PM +0100, Aidan MacDonald wrote:
> Call sub_irq_reg() instead of calculating the offset of the register
> to avoid relying on the fact that sub_irq_reg() is a linear function.
Seems like unmask_reg is the only register whose address is not calculated
using sub_irq_reg(). Switching to using sub_irq_reg() will bring it in line
with the other calculations.
Could you please incorporate this info in your commit message as well? This
should be the rationale for this change; that it allows for the get_irq_reg()
patch should be secondary.
The change seems okay to me, but I'd ideally like someone to pick this up and
test it out just to make sure it doesn't break existing behaviour for them.
Thank you.
Guru Das.
Powered by blists - more mailing lists