Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: "Vladislav Leonov" <vlad@zlab.su>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Joshua Crofts" <joshua.crofts1@gmail.com>,
	"Simon Glass" <sjg@chromium.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Fix RV1106 SAR-ADC support
Date: Tue, 1 Sep 2026 02:18:46 +0100	[thread overview]
Message-ID: <20260901021846.59b71f5b@jic23-huawei> (raw)
In-Reply-To: <5330090.ejJDZkT8p0@diego>

On Mon, 31 Aug 2026 10:17:17 +0200
Heiko Stübner <heiko@sntech.de> wrote:

> Hi Jonathan,
> 
> Am Montag, 31. August 2026, 03:55:57 Mitteleuropäische Sommerzeit schrieb Jonathan Cameron:
> > On Sun, 23 Aug 2026 15:20:31 +0300
> > Vladislav Leonov <vlad@zlab.su> wrote:
> >   
> > > This series fixes the support for the RV1106 SAR-ADC in the
> > > rockchip_saradc driver and its device tree bindings.  
> > 
> > I debated how to apply this.  Technically patch 3 is a fix, 2 is an enabler
> > and 1 is also a fix, but one for something that we just effectively patched
> > out from running in patch 3.
> > 
> > So in the end I'm thinking take this the slow path for next cycle.  Shout
> > if anyone thinks this should go in during the -RCs and whether all 3
> > should do so or just patches 2 and 3 (leaving us without driver support for
> > now).
> > 
> > Applied to the testing branch of iio.git  
> 
> I guess I should shout then ;-) .
> 
> DT-Binding patches are sort of independent of the driver change and
> are considered API which should not change after the fact.
> 
> Our DTs (but also ones possibly contained in firmware somewhere) are
> validated against the binding and it seems the correct compartible goes
> from 
>     "rockchip,rv1106-saradc", " rockchip,rk3588-saradc"
> to
>     "rockchip,rv1106-saradc"
> 
> As the fixed commit is part of 7.3-rc1, I guess it would be nice to
> have patches 2+3 in 7.3 and patch 1 can wait for 7.4 .
> 
> We don't need the driver support (dt-nodes just doesn't bind to
> anything), but it would be nice to not proliferate the wrong binding in
> an actual release.

Ah. I should have checked when the original bug went in.
As it's this current cycle, what you say is indeed an easy fix.

Applied 2-3 to the fixes-togreg branch and left 1 in the testing
branch for 7.4.

Thanks

Jonathan

> 
> 
> my 2ct :-)
> Heiko
> 
> 
> 


      reply	other threads:[~2026-09-01  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 12:20 [PATCH v2 0/3] Fix RV1106 SAR-ADC support Vladislav Leonov
2026-08-23 12:20 ` [PATCH v2 1/3] iio: adc: rockchip_saradc: Add support for RV1106 Vladislav Leonov
2026-08-23 12:20 ` [PATCH v2 2/3] dt-bindings: iio: adc: rockchip-saradc: Group single-entries into an enum list Vladislav Leonov
2026-08-24 16:38   ` Conor Dooley
2026-08-23 12:20 ` [PATCH v2 3/3] dt-bindings: iio: adc: rockchip-saradc: Fix RV1106 compatible Vladislav Leonov
2026-08-24 16:38   ` Conor Dooley
2026-08-31  1:55 ` [PATCH v2 0/3] Fix RV1106 SAR-ADC support Jonathan Cameron
2026-08-31  8:17   ` Heiko Stübner
2026-09-01  1:18     ` Jonathan Cameron [this message]

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=20260901021846.59b71f5b@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=heiko@sntech.de \
    --cc=joshua.crofts1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=sjg@chromium.org \
    --cc=vlad@zlab.su \
    /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