linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Andy Gross <agross@kernel.org>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 6/9] ARM: dts: qcom-pma8084: Drop incorrect use of io-channel-ranges
Date: Sat, 28 Nov 2020 18:59:40 +0000	[thread overview]
Message-ID: <20201128185940.401c0465@archlinux> (raw)
In-Reply-To: <X8KXMrFg1g8OsjZj@builder.lan>

On Sat, 28 Nov 2020 12:30:10 -0600
Bjorn Andersson <bjorn.andersson@linaro.org> wrote:

> 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.

No problem. I've added your tag to the yaml change.

Thanks,

Jonathan


> 
> 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>;  
> >   


      reply	other threads:[~2020-11-28 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201115192951.1073632-1-jic23@kernel.org>
     [not found] ` <20201115192951.1073632-7-jic23@kernel.org>
2020-11-28 15:37   ` [PATCH 6/9] ARM: dts: qcom-pma8084: Drop incorrect use of io-channel-ranges Jonathan Cameron
2020-11-28 18:30     ` Bjorn Andersson
2020-11-28 18:59       ` 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=20201128185940.401c0465@archlinux \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.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).