[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220614130018.4b29345d@jic23-huawei>
Date: Tue, 14 Jun 2022 13:00:18 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: <Claudiu.Beznea@...rochip.com>
Cc: <Eugen.Hristev@...rochip.com>, <lars@...afoo.de>,
<Nicolas.Ferre@...rochip.com>, <alexandre.belloni@...tlin.com>,
<robh+dt@...nel.org>, <krzk+dt@...nel.org>,
<ludovic.desroches@...el.com>, <linux-iio@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 07/16] iio: adc: at91-sama5d2_adc: simplify the code in
at91_adc_read_info_raw()
On Tue, 14 Jun 2022 08:49:03 +0000
<Claudiu.Beznea@...rochip.com> wrote:
> On 11.06.2022 20:54, Jonathan Cameron wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Thu, 9 Jun 2022 11:32:04 +0300
> > Claudiu Beznea <claudiu.beznea@...rochip.com> wrote:
> >
> >> Simplify a bit the code in at91_adc_read_info_raw() by reducing the
> >> number of lines of code.
> >>
> >> Signed-off-by: Claudiu Beznea <claudiu.beznea@...rochip.com>
> >
> > I'm not convinced this is worth while, but there are some lesser
> > steps visible in this patch that probably are.
> >
> > Given your earlier reorg to move at01_adc_adjust_val_osr() under the locks,
> > you can now move the locks to the caller, thus not needing to handle them
> > separately in all the exit paths.
>
> OK, I'll give it a try. With this, would you prefer to still keep this patch?
>
No. I don't think it will bring enough benefit for the loss of readability.
Having moved the locking, there will only be a few repeated lines.
Jonathan
Powered by blists - more mailing lists