linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 2/7] dt-bindings: iio: rockchip-saradc: add support for rk3328
Date: Sun, 19 Mar 2017 10:34:22 +0000	[thread overview]
Message-ID: <fff0d197-c88e-fd04-0f56-c4fbc982bae4@kernel.org> (raw)
In-Reply-To: <8664375.8vdE6CQfX9@phil>

On 16/03/17 08:28, Heiko Stuebner wrote:
> Am Mittwoch, 15. M?rz 2017, 18:03:52 CET schrieb cl at rock-chips.com:
>> From: Chen Liang <cl@rock-chips.com>
>>
>> The rk3328 saradc is the same as rk3399.
>>
>> Signed-off-by: Chen Liang <cl@rock-chips.com>
>> ---
>>  Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
>> b/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt index
>> 205593f..f81bc20 100644
>> --- a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
>> +++ b/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
>> @@ -5,6 +5,7 @@ Required properties:
>>     - "rockchip,saradc": for rk3188, rk3288
>>     - "rockchip,rk3066-tsadc": for rk3036
>>     - "rockchip,rk3399-saradc": for rk3399
>> +   - "rockchip,rk3328-saradc", "rockchip,rk3399-saradc": for rk3328
> 
> not sure how iio people see that, but I would suggest keeping the order, so 
> put rk3328 above rk3399.
In my case I'm not that fussed either way. Still if this list keeps growing
I can see it would be better to keep it in numeric order!

Jonathan
> 
> Heiko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2017-03-19 10:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 10:03 [PATCH v1 0/7] initialize dtsi file and dts file for RK3328 SoCs cl at rock-chips.com
2017-03-15 10:03 ` [PATCH v1 1/7] include: dt-bindings: Add pin function index definition for rockchip pinctrl cl at rock-chips.com
2017-03-16  8:02   ` Heiko Stübner
2017-03-15 10:03 ` [PATCH v1 2/7] dt-bindings: iio: rockchip-saradc: add support for rk3328 cl at rock-chips.com
2017-03-16  8:28   ` Heiko Stuebner
2017-03-19 10:34     ` Jonathan Cameron [this message]
2017-03-15 10:03 ` [PATCH v1 3/7] dt-bindings: i2c: rk3x: " cl at rock-chips.com
2017-03-16  8:29   ` Heiko Stuebner
2017-03-15 10:03 ` [PATCH v1 4/7] dt-bindings: soc: rockchip: grf: " cl at rock-chips.com
2017-03-15 11:11 ` [PATCH v1 0/7] initialize dtsi file and dts file for RK3328 SoCs Heiko Stübner
2017-03-16  1:44 ` [PATCH v1 5/7] arm64: dts: rockchip: add core dtsi " cl at rock-chips.com
2017-03-16 16:15   ` Andre Przywara
2017-03-16  1:45 ` [PATCH v1 6/7] arm64: dts: rockchip: add dts file for RK3328 evaluation board cl at rock-chips.com
2017-03-16 16:18   ` Andre Przywara
2017-03-17  2:26     ` 陈亮
2017-03-17  8:45       ` Heiko Stuebner
2017-03-21  7:59         ` 陈亮
2017-03-21  8:57           ` Heiko Stübner
2017-03-16  1:45 ` [PATCH v1 7/7] dt-bindings: document rockchip rk3328-evb board cl at rock-chips.com

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=fff0d197-c88e-fd04-0f56-c4fbc982bae4@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).