From: Jonathan Cameron <jic23@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <noname.nuno@gmail.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 0/3] iio: adc: ad7124: Fix 3dB filter frequency reading
Date: Mon, 31 Mar 2025 11:02:14 +0100 [thread overview]
Message-ID: <20250331110214.1eec2513@jic23-huawei> (raw)
In-Reply-To: <fgd3vr46ijt3kr6onvtulmfulgbr2jpshcyk3dr2pvz7vqs2fq@mka4q2zqmpwe>
On Mon, 24 Mar 2025 10:44:52 +0100
Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
> Hello Jonathan,
>
> On Mon, Mar 17, 2025 at 07:00:31PM +0000, Jonathan Cameron wrote:
> > On Mon, 17 Mar 2025 12:52:46 +0100
> > Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
> >
> > > Hello,
> > >
> > > (implicit) v1 of this patch set is available at
> > > https://lore.kernel.org/linux-iio/cover.1741801853.git.u.kleine-koenig@baylibre.com
> > > .
> > >
> > > Changes since then:
> > >
> > > - Reorder patches to have the cleanup ("Make register naming
> > > consistent") last
> > > - Drop write support for the filter_low_pass_3db_frequency property
> > > which is completely broken.
> > > - trivially rebase to todays iio/togreg
> > >
> > > I wonder if there is a way to remove the writable permission of the
> > > filter_low_pass_3db_frequency sysfs file instead of erroring out when a
> > > value is written. Hints welcome.
> >
> > Unfortunately not. With a lot of hindsight that is a flaw in the way
> > we generate sysfs attributes. IIRC when hwmon added similar they
> > avoided that trap. To retrofit it onto IIO now we'd have to have
> > some form of complex permissions query or duplicate all the masks
> > to allow r and w separately.
>
> OK, fine for me, so I didn't miss anything :-)
>
> I have another patch in my queue for ad7124. For that it would be great
> to know if you intend to apply this patch set. If yes, I continue to
> build on top of this stack.
Sorry for slow reply. Bunch of travel (and being a tourist on either end
of the work bit ;)
Subject to the question on patch 1 from Marcelo I'm fine with this.
I'll probably take all 3 for next merge window though as patch 1 is
a minor fix I think in something that people probably haven't really
been using and splitting it makes for a messy cycle.
Jonathan
>
> Best regards
> Uwe
next prev parent reply other threads:[~2025-03-31 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 11:52 [PATCH v2 0/3] iio: adc: ad7124: Fix 3dB filter frequency reading Uwe Kleine-König
2025-03-17 11:52 ` [PATCH v2 1/3] " Uwe Kleine-König
2025-03-26 18:20 ` Marcelo Schmitt
2025-03-31 13:38 ` Uwe Kleine-König
2025-03-31 14:40 ` Marcelo Schmitt
2025-03-17 11:52 ` [PATCH v2 2/3] iio: adc: ad7124: Remove ability to write filter_low_pass_3db_frequency Uwe Kleine-König
2025-03-26 18:35 ` Marcelo Schmitt
2025-03-31 9:53 ` Jonathan Cameron
2025-03-17 11:52 ` [PATCH v2 3/3] iio: adc: ad7124: Make register naming consistent Uwe Kleine-König
2025-03-17 19:00 ` [PATCH v2 0/3] iio: adc: ad7124: Fix 3dB filter frequency reading Jonathan Cameron
2025-03-24 9:44 ` Uwe Kleine-König
2025-03-31 10:02 ` Jonathan Cameron [this message]
2025-04-06 10:54 ` Jonathan Cameron
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=20250331110214.1eec2513@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=u.kleine-koenig@baylibre.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