From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Mehdi Djait <mehdi.djait.k@gmail.com>,
krzysztof.kozlowski+dt@linaro.org,
andriy.shevchenko@linux.intel.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/5] iio: accel: kionix-kx022a: Add a function to retrieve number of bytes in buffer
Date: Sat, 22 Apr 2023 18:42:06 +0100 [thread overview]
Message-ID: <20230422184206.39366500@jic23-huawei> (raw)
In-Reply-To: <20230422183626.2b351521@jic23-huawei>
On Sat, 22 Apr 2023 18:36:26 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Fri, 21 Apr 2023 09:14:10 +0300
> Matti Vaittinen <mazziesaccount@gmail.com> wrote:
>
> > Hi Mehdi,
> >
> > Thanks for the v2!
> >
> > On 4/20/23 23:22, Mehdi Djait wrote:
> > > Since Kionix accelerometers use various numbers of bits to report data, a
> > > device-specific function is required.
> >
> > I think this is the right approach. Thanks for adding this
> > device-specific function.
> >
> > > Move the driver's private data to the header file to support the new function.
> >
> > Hmm. Why this move is necessary? I didn't immediately spot this struct
> > being used outside this C-file. I'd rather saw the struct in C-file if
> > possible.
> >
> > > Make the allocation of the "buffer" array in the fifo_flush function dynamic
> > > and more generic.
> > >
> > > Signed-off-by: Mehdi Djait <mehdi.djait.k@gmail.com>
> > > ---
> > > v2:
> > > - separated this change from the chip_info introduction and made it a patch in v2
> >
> > I am unsure if this separation was needed. I'd only separate the "naming
> > changes" which bring no changes to code flow, and then patches which are
> > fixes and need to be backported (to minimize backporting effort and
> > impact to stable branches). Well, I am fine with this separation though,
> > seems like I am just making a noise here :).
>
> I prefer them split. I want to see a noop patch for refactors. It's easier
> to quickly check it really makes no functional change. Adding new
> structures for a new device just adds noise to checking that.
Oops. I got the patches confused. Ignore that comment.
>
>
> >
> > > - changed the function from generic implementation for to device-specific one
> > > - removed blank lines pointed out by checkpatch
> > > - changed the allocation of the "buffer" array in __kx022a_fifo_flush
> > >
> > > drivers/iio/accel/kionix-kx022a.c | 72 +++++++++++++------------------
> > > drivers/iio/accel/kionix-kx022a.h | 37 ++++++++++++++++
> > > 2 files changed, 66 insertions(+), 43 deletions(-)
> > >
> > > diff --git a/drivers/iio/accel/kionix-kx022a.c b/drivers/iio/accel/kionix-kx022a.c
> > > index 7f9a2c29790b..1c81ea1657b9 100644
> > > --- a/drivers/iio/accel/kionix-kx022a.c
> > > +++ b/drivers/iio/accel/kionix-kx022a.c
> > > @@ -150,36 +150,6 @@ static const struct regmap_config kx022a_regmap_config = {
> > > .cache_type = REGCACHE_RBTREE,
> > > };
> >
> > Yours,
> > -- Matti
> >
>
next prev parent reply other threads:[~2023-04-22 17:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 20:22 [PATCH v2 0/5] iio: accel: Add support for Kionix/ROHM KX132-1211 accelerometer Mehdi Djait
2023-04-20 20:22 ` [PATCH v2 1/5] dt-bindings: iio: Add " Mehdi Djait
2023-04-21 3:36 ` Matti Vaittinen
2023-04-21 8:12 ` Krzysztof Kozlowski
2023-04-20 20:22 ` [PATCH v2 2/5] iio: accel: kionix-kx022a: Warn on failed matches and assume compatibility Mehdi Djait
2023-04-21 3:44 ` Matti Vaittinen
2023-04-22 17:26 ` Jonathan Cameron
2023-04-22 17:28 ` Jonathan Cameron
2023-04-23 20:59 ` Mehdi Djait
2023-04-20 20:22 ` [PATCH v2 3/5] iio: accel: kionix-kx022a: Refactor driver and add chip_info structure Mehdi Djait
2023-04-21 6:19 ` Matti Vaittinen
2023-04-22 17:32 ` Jonathan Cameron
2023-04-23 21:01 ` Mehdi Djait
2023-04-20 20:22 ` [PATCH v2 4/5] iio: accel: kionix-kx022a: Add a function to retrieve number of bytes in buffer Mehdi Djait
2023-04-21 6:14 ` Matti Vaittinen
2023-04-22 17:36 ` Jonathan Cameron
2023-04-22 17:42 ` Jonathan Cameron [this message]
2023-04-23 22:06 ` Mehdi Djait
2023-04-22 17:46 ` Jonathan Cameron
2023-04-23 22:05 ` Mehdi Djait
2023-04-20 20:22 ` [PATCH v2 5/5] iio: accel: Add support for Kionix/ROHM KX132-1211 accelerometer Mehdi Djait
2023-04-21 23:19 ` kernel test robot
2023-04-22 16:09 ` Andy Shevchenko
2023-04-23 20:56 ` Mehdi Djait
2023-04-24 14:56 ` Mehdi Djait
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230422184206.39366500@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=mehdi.djait.k@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox