public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Jorge Marques" <gastmaier@gmail.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jorge Marques" <jorge.marques@analog.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-pwm@vger.kernel.org
Subject: Re: [PATCH v2 1/5] Documentation: ABI: add oversampling frequency in sysfs-bus-iio
Date: Mon, 5 May 2025 13:39:58 +0100	[thread overview]
Message-ID: <20250505133958.01dffb57@jic23-huawei> (raw)
In-Reply-To: <CAHp75VcZM+4Br2-RMKZixEd1=x3_exbWZkEFw1U_NrFtsejkUg@mail.gmail.com>

On Wed, 30 Apr 2025 01:03:07 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Tue, Apr 29, 2025 at 6:40 PM David Lechner <dlechner@baylibre.com> wrote:
> >
> > On 4/29/25 8:47 AM, Jorge Marques wrote:  
> > >
> > > Hi Andy,
> > >
> > > I agree with your suggestion, and in this case the appropriate kernel
> > > version is 3.10.
> > >  
> > >>  
> > >>> +What:              /sys/bus/iio/devices/iio:deviceX/oversampling_frequency
> > >>> +KernelVersion:     6.15  
> > >>
> > >> Then why don't you put the real version of the first release that has it?
> > >>  
> > >>> +Contact:   linux-iio@vger.kernel.org
> > >>> +Description:
> > >>> +           Some devices have internal clocks for oversampling.
> > >>> +           Sets the resulting frequency in Hz to trigger a conversion used by
> > >>> +           the oversampling filter.
> > >>> +           If the device has a fixed internal clock or is computed based on
> > >>> +           the sampling frequency parameter, the parameter is read only.
> > >>> +
> > >>> +What:              /sys/bus/iio/devices/iio:deviceX/oversampling_frequency_available
> > >>> +KernelVersion:     6.15  
> > >>
> > >> Ditto.
> > >>  
> > >>> +Contact:   linux-iio@vger.kernel.org
> > >>> +Description:
> > >>> +           Hardware dependent values supported by the oversampling
> > >>> +           frequency.  
> >
> >
> > I don't see oversampling_frequency used in any existing driver, so how could
> > it be introduced in kernel 3.10? I think you confuse it with
> > events/sampling_frequency.
> >
> > oversampling_frequency is new and so 6.16 should be correct if Jonathan picks
> > this up in the next few weeks, otherwise it will be 6.17.  
> 
> If this is the case, the whole commit message should be revisited.
> 
Yeah. That last bit about the existing drivers is talking about unrelated
ABI.

Jonathan


  reply	other threads:[~2025-05-05 12:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 11:34 [PATCH v2 0/5] Add support for AD4052 device family Jorge Marques
2025-04-22 11:34 ` [PATCH v2 1/5] Documentation: ABI: add oversampling frequency in sysfs-bus-iio Jorge Marques
2025-04-22 15:50   ` Andy Shevchenko
2025-04-29 13:47     ` Jorge Marques
2025-04-29 15:40       ` David Lechner
2025-04-29 22:03         ` Andy Shevchenko
2025-05-05 12:39           ` Jonathan Cameron [this message]
2025-04-25 21:16   ` David Lechner
2025-04-29 13:47     ` Jorge Marques
2025-04-22 11:34 ` [PATCH v2 2/5] iio: code: mark iio_dev as const in iio_buffer_enabled Jorge Marques
2025-04-22 15:51   ` Andy Shevchenko
2025-04-26 15:45   ` Jonathan Cameron
2025-06-02  9:48     ` Jorge Marques
2025-04-22 11:34 ` [PATCH v2 3/5] dt-bindings: iio: adc: Add adi,ad4052 Jorge Marques
2025-04-25 20:58   ` Rob Herring (Arm)
2025-04-25 22:50   ` David Lechner
2025-04-29 13:48     ` Jorge Marques
2025-04-29 15:45       ` David Lechner
2025-06-02  9:17         ` Jorge Marques
2025-06-02 15:17           ` David Lechner
2025-06-02 16:32             ` Jorge Marques
2025-06-02 17:23               ` David Lechner
2025-06-03  7:29                 ` Jorge Marques
2025-06-03 13:27                   ` David Lechner
2025-04-22 11:34 ` [PATCH v2 4/5] docs: iio: new docs for ad4052 driver Jorge Marques
2025-04-25 21:44   ` David Lechner
2025-04-29 13:49     ` Jorge Marques
2025-04-29 15:50       ` David Lechner
2025-04-22 11:34 ` [PATCH v2 5/5] iio: adc: add support for ad4052 Jorge Marques
2025-04-22 16:33   ` Andy Shevchenko
2025-04-29 13:49     ` Jorge Marques
2025-04-25 23:13   ` David Lechner
2025-06-02 11:16     ` Jorge Marques
2025-06-02 15:33       ` David Lechner
2025-04-26 16:03   ` Jonathan Cameron
2025-06-02 10:50     ` Jorge Marques
2025-05-16 10:11   ` Uwe Kleine-König
2025-06-02 10:38     ` Jorge Marques

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=20250505133958.01dffb57@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gastmaier@gmail.com \
    --cc=jorge.marques@analog.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=ukleinek@kernel.org \
    /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