From: "Heiko Stübner" <heiko@sntech.de>
To: Jonathan Cameron <jic23@kernel.org>, Simon Xue <xxm@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, Johan Jonker <jbx6244@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, Simon Xue <xxm@rock-chips.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: adc: rockchip-saradc: add description for rk3568
Date: Mon, 12 Jul 2021 09:01:00 +0200 [thread overview]
Message-ID: <5271950.MlmRxi5KL8@diego> (raw)
In-Reply-To: <20210712014437.97427-1-xxm@rock-chips.com>
Am Montag, 12. Juli 2021, 03:44:37 CEST schrieb Simon Xue:
> Add description for rk3568 saradc.
>
> Signed-off-by: Simon Xue <xxm@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml b/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml
> index 1bb76197787b..e512a14e41b4 100644
> --- a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml
> @@ -20,6 +20,7 @@ properties:
> - rockchip,px30-saradc
> - rockchip,rk3308-saradc
> - rockchip,rk3328-saradc
> + - rockchip,rk3568-saradc
> - rockchip,rv1108-saradc
> - const: rockchip,rk3399-saradc
>
>
next prev parent reply other threads:[~2021-07-12 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 1:44 [PATCH v2 1/2] dt-bindings: iio: adc: rockchip-saradc: add description for rk3568 Simon Xue
2021-07-12 1:45 ` [PATCH v2 2/2] iio: adc: rockchip_saradc: add support for rk3568 saradc Simon Xue
2021-07-12 7:02 ` Heiko Stübner
2021-07-12 7:01 ` Heiko Stübner [this message]
2021-07-15 16:23 ` [PATCH v2 1/2] dt-bindings: iio: adc: rockchip-saradc: add description for rk3568 Rob Herring
2021-07-17 17:04 ` 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=5271950.MlmRxi5KL8@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=xxm@rock-chips.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).