[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZOdfeaW6AxE4eeqw@smile.fi.intel.com>
Date: Thu, 24 Aug 2023 16:47:37 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mehdi Djait <mehdi.djait.k@...il.com>
Cc: Matti Vaittinen <mazziesaccount@...il.com>, jic23@...nel.org,
krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
lars@...afoo.de, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v8 6/7] iio: accel: kionix-kx022a: Add a function to
retrieve number of bytes in buffer
On Thu, Aug 24, 2023 at 03:44:29PM +0200, Mehdi Djait wrote:
> On Thu, Aug 24, 2023 at 3:39 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Thu, Aug 24, 2023 at 03:52:56PM +0300, Matti Vaittinen wrote:
> > > On 8/24/23 14:58, Andy Shevchenko wrote:
> > > > On Wed, Aug 23, 2023 at 11:16:40PM +0200, Mehdi Djait wrote:
...
> > I see. I think my confusion can be easily cured by renaming the callback to
> >
> > get_amount_bytes_in_fifo()
> >
> > or
> >
> > get_bytes_in_fifo()
> >
> > or alike.
>
> or leave it as is. The function is documented:
> + * @get_fifo_bytes: function pointer to get number of bytes in the FIFO buffer
Do you find it unambiguous? I do not.
Still needs more words to explain if it's a capacity of FIFO or is it amount of
valid bytes for the current transfer or what?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists