From: Jonathan Cameron <jic23@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Mingjin Yang <mingjin.yang@unisoc.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
magicyangmingjin@gmail.com, Ling_Ling.Xu@unisoc.com,
Jinfeng.Lin1@unisoc.com, Yangbin.Li@unisoc.com,
Jiansheng.Wu@unisoc.com, Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V0 1/2] dt-bindings: iio: adc: Add support for ump518 pmic adc
Date: Mon, 28 Aug 2023 15:40:10 +0100 [thread overview]
Message-ID: <20230828153930.73d879ba@jic23-huawei> (raw)
In-Reply-To: <20230816-dastardly-escapade-75597e244088@spud>
On Wed, 16 Aug 2023 15:44:55 +0100
Conor Dooley <conor@kernel.org> wrote:
> On Wed, Aug 16, 2023 at 04:02:24PM +0800, Mingjin Yang wrote:
> > Add ump518 pmic adc description and sample in dt-bindings.
ADC
Description? I'm seeing the compatible only which doesn't seem like
a description to me.
> >
> > Signed-off-by: Mingjin Yang <mingjin.yang@unisoc.com>
> > ---
> > Documentation/devicetree/bindings/iio/adc/sprd,sc2720-adc.yaml | 2 ++
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Thanks,
> Conor.
>
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/adc/sprd,sc2720-adc.yaml b/Documentation/devicetree/bindings/iio/adc/sprd,sc2720-adc.yaml
> > index 8181cf9a8e07..f28d188d83da 100644
> > --- a/Documentation/devicetree/bindings/iio/adc/sprd,sc2720-adc.yaml
> > +++ b/Documentation/devicetree/bindings/iio/adc/sprd,sc2720-adc.yaml
> > @@ -21,6 +21,7 @@ properties:
> > - sprd,sc2730-adc
> > - sprd,sc2731-adc
> > - sprd,ump9620-adc
> > + - sprd,ump518-adc
alpha-numeric ordering probably worth retaining.
So I'd move this and the case below up one line.
Thanks,
Jonathan
> >
> > reg:
> > maxItems: 1
> > @@ -46,6 +47,7 @@ allOf:
> > contains:
> > enum:
> > - sprd,ump9620-adc
> > + - sprd,ump518-adc
> > then:
> > properties:
> > nvmem-cells:
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2023-08-28 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 8:02 [PATCH V0 0/2] Add support for UMP serise pmic adc Mingjin Yang
2023-08-16 8:02 ` [PATCH V0 1/2] dt-bindings: iio: adc: Add support for ump518 " Mingjin Yang
2023-08-16 14:44 ` Conor Dooley
2023-08-28 14:40 ` Jonathan Cameron [this message]
2023-08-16 8:02 ` [PATCH V0 2/2] iio: adc: sprd_pmic_adc: Add support for UMP serise " Mingjin Yang
2023-08-16 14:07 ` kernel test robot
2023-08-28 14:38 ` Jonathan Cameron
2023-08-28 15:57 ` Jonathan Cameron
2023-08-30 7:15 ` 杨明金
2023-09-03 11:14 ` Jonathan Cameron
2023-09-05 2:59 ` 杨明金
2023-09-10 13:57 ` 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=20230828153930.73d879ba@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jiansheng.Wu@unisoc.com \
--cc=Jinfeng.Lin1@unisoc.com \
--cc=Ling_Ling.Xu@unisoc.com \
--cc=Yangbin.Li@unisoc.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magicyangmingjin@gmail.com \
--cc=mingjin.yang@unisoc.com \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=zhang.lyra@gmail.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;
as well as URLs for NNTP newsgroup(s).