From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
robh+dt@kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/9] ARM: dts: qcom-pma8084: Drop incorrect use of io-channel-ranges
Date: Sat, 28 Nov 2020 12:30:10 -0600 [thread overview]
Message-ID: <X8KXMrFg1g8OsjZj@builder.lan> (raw)
In-Reply-To: <20201128153702.7d144f68@archlinux>
On Sat 28 Nov 09:37 CST 2020, Jonathan Cameron wrote:
> On Sun, 15 Nov 2020 19:29:48 +0000
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > This property is used by io-channel consumers, not providers so should
> > not present here. Note dt_schema will now detect this error as there
> > is a dependency between this property and io-channels.
> >
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Cc: Andy Gross <andy.gross@linaro.org>
> > Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> +CC Andy on an up to date email. Also added linux-arm-msm
> which I should have cc'd in the first place.
>
> I've taken the yaml fix related to this so just a question of
> cleaning up this loose end in the dtsi
>
Thanks Jonathan, I missed your patches earlier. The yaml change looks
correct and I've merged this for 5.11.
Regards,
Bjorn
> Thanks,
>
> Jonathan
>
> > ---
> > arch/arm/boot/dts/qcom-pma8084.dtsi | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/arch/arm/boot/dts/qcom-pma8084.dtsi b/arch/arm/boot/dts/qcom-pma8084.dtsi
> > index ea1ca166165c..e921c5e93a5d 100644
> > --- a/arch/arm/boot/dts/qcom-pma8084.dtsi
> > +++ b/arch/arm/boot/dts/qcom-pma8084.dtsi
> > @@ -68,7 +68,6 @@ pma8084_vadc: vadc@3100 {
> > #address-cells = <1>;
> > #size-cells = <0>;
> > #io-channel-cells = <1>;
> > - io-channel-ranges;
> >
> > die_temp {
> > reg = <VADC_DIE_TEMP>;
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-28 18:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 19:29 [PATCH 0/9] dt-bindings: IIO: Drop wrong use of io-channel-ranges then drop it as well Jonathan Cameron
2020-11-15 19:29 ` [PATCH 1/9] dt-bindings:iio:qcom-spmi-vadc drop incorrect io-channel-ranges from example Jonathan Cameron
2020-11-28 15:33 ` Jonathan Cameron
2020-11-28 18:26 ` Bjorn Andersson
2020-11-15 19:29 ` [PATCH 2/9] dt-bindings:iio:samsung, exynos-adc: drop missuse of io-channel-ranges Jonathan Cameron
2020-11-17 9:49 ` [PATCH 2/9] dt-bindings:iio:samsung,exynos-adc: " Krzysztof Kozlowski
2020-11-28 15:35 ` Jonathan Cameron
2020-11-15 19:29 ` [PATCH 3/9] ARM: dts: Cygnus: Drop incorrect io-channel-ranges property Jonathan Cameron
2020-11-16 3:23 ` Florian Fainelli
2020-11-16 9:44 ` Jonathan Cameron
2020-11-15 19:29 ` [PATCH 4/9] ARM: dts: exynos: Drop incorrect use of io-channel-ranges Jonathan Cameron
2020-11-17 19:45 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [PATCH 5/9] ARM: dts: s5pv210: Drop incorrect use of io-channel-ranges property Jonathan Cameron
2020-11-17 19:46 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [PATCH 6/9] ARM: dts: qcom-pma8084: Drop incorrect use of io-channel-ranges Jonathan Cameron
2020-11-28 15:37 ` Jonathan Cameron
2020-11-28 18:30 ` Bjorn Andersson [this message]
2020-11-28 18:59 ` Jonathan Cameron
2020-11-15 19:29 ` [PATCH 7/9] ARM: dts: s5pv210-aries: Drop unneeded io-channel-ranges property Jonathan Cameron
2020-11-17 19:47 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [PATCH 8/9] arm64: dts: exynos: Drop incorrect use of " Jonathan Cameron
2020-11-17 19:48 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [RFC PATCH 9/9] iio: inkern: Drop io-channel-ranges dt property support Jonathan Cameron
2021-02-21 16:31 ` 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=X8KXMrFg1g8OsjZj@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).