From: Caesar Wang <caesar.upstream@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Caesar Wang <wxt@rock-chips.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
hl@rock-chips.com, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
sonnyrao@chromium.org, jeffy.chen@rock-chips.com,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-rockchip@lists.infradead.org,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org, keescook@google.com,
cf@rock-chips.com, jay.xu@rock-chips.com, leozwang@google.com
Subject: Re: [PATCH v4 9/9] ARM: dts: rockchip: support the spi for rk3036
Date: Mon, 1 Feb 2016 14:32:59 +0800 [thread overview]
Message-ID: <56AEFC1B.60407@gmail.com> (raw)
In-Reply-To: <3295129.SttO6ack9z@phil>
Heiko,
在 2016年01月31日 19:06, Heiko Stuebner 写道:
> Hi Caesar,
>
> Am Donnerstag, 28. Januar 2016, 16:43:38 schrieb Caesar Wang:
[...]
>
> memory {
> @@ -485,6 +486,23 @@
> status = "disabled";
> };
>
> + spi: spi@20074000 {
> + compatible = "rockchip,rockchip-spi";
> + reg = <0x20074000 0x1000>;
> + interrupts = <GIC_SPI 23 IRQ_TYPE_LEVEL_HIGH>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&spi_txd &spi_rxd &spi_clk &spi_cs0 &spi_cs1>;
> Do we really want to enable both chip-selects by default?
>
> On the rk3288 Lin Huang wrote:
> * It's assumed that most users of the SPI ports are using chip select
> 0. Thus the default pinctrl for the ports enables chip select 0
> (but not chip select 1 on ports that have it). If a board wants to
> use chip select 1 or wants a GPIO chip select the board should
> override the pinctrl (just like boards can override UART pinctrl if
> they have hardware flow control).
>
> Do we expect again mostly a use of cs0 or will in the major cases both chip-
> selects be needed?
Sound resonable.
In general, every cs and spi devices should be the one match one.
That should be resonable if we want to use chip select 1 or want a GPIO chip select the board should
override the pinctrl.
>> + num-cs = <2>;
>> + clocks =<&cru PCLK_SPI>, <&cru SCLK_SPI>;
>> + clock-names = "apb-pclk","spi_pclk";
>> + dmas = <&pdma 8>, <&pdma 9>;
>> + #dma-cells = <2>;
> What do you need #dma-cells for? This is not a dma-controller :-)
Fixed.
>
>
>> + dma-names = "tx", "rx";
>> + status = "disabled";
>> + };
>
> Also I'd suggest an ordering like:
>
> + spi: spi@20074000 {
> + compatible = "rockchip,rockchip-spi";
> + reg = <0x20074000 0x1000>;
> + interrupts = <GIC_SPI 23 IRQ_TYPE_LEVEL_HIGH>;
> + clocks =<&cru PCLK_SPI>, <&cru SCLK_SPI>;
> + clock-names = "apb-pclk","spi_pclk";
> + dmas = <&pdma 8>, <&pdma 9>;
> + dma-names = "tx", "rx";
> + num-cs = <2>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&spi_txd &spi_rxd &spi_clk &spi_cs0 &spi_cs1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + status = "disabled";
> + };
Okay, I will remove the cs1/num-cs in here.
Thanks.
-
Caesar
>
> Heiko
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
--
Thanks,
Caesar
WARNING: multiple messages have this Message-ID (diff)
From: caesar.upstream@gmail.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 9/9] ARM: dts: rockchip: support the spi for rk3036
Date: Mon, 1 Feb 2016 14:32:59 +0800 [thread overview]
Message-ID: <56AEFC1B.60407@gmail.com> (raw)
In-Reply-To: <3295129.SttO6ack9z@phil>
Heiko,
? 2016?01?31? 19:06, Heiko Stuebner ??:
> Hi Caesar,
>
> Am Donnerstag, 28. Januar 2016, 16:43:38 schrieb Caesar Wang:
[...]
>
> memory {
> @@ -485,6 +486,23 @@
> status = "disabled";
> };
>
> + spi: spi at 20074000 {
> + compatible = "rockchip,rockchip-spi";
> + reg = <0x20074000 0x1000>;
> + interrupts = <GIC_SPI 23 IRQ_TYPE_LEVEL_HIGH>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&spi_txd &spi_rxd &spi_clk &spi_cs0 &spi_cs1>;
> Do we really want to enable both chip-selects by default?
>
> On the rk3288 Lin Huang wrote:
> * It's assumed that most users of the SPI ports are using chip select
> 0. Thus the default pinctrl for the ports enables chip select 0
> (but not chip select 1 on ports that have it). If a board wants to
> use chip select 1 or wants a GPIO chip select the board should
> override the pinctrl (just like boards can override UART pinctrl if
> they have hardware flow control).
>
> Do we expect again mostly a use of cs0 or will in the major cases both chip-
> selects be needed?
Sound resonable.
In general, every cs and spi devices should be the one match one.
That should be resonable if we want to use chip select 1 or want a GPIO chip select the board should
override the pinctrl.
>> + num-cs = <2>;
>> + clocks =<&cru PCLK_SPI>, <&cru SCLK_SPI>;
>> + clock-names = "apb-pclk","spi_pclk";
>> + dmas = <&pdma 8>, <&pdma 9>;
>> + #dma-cells = <2>;
> What do you need #dma-cells for? This is not a dma-controller :-)
Fixed.
>
>
>> + dma-names = "tx", "rx";
>> + status = "disabled";
>> + };
>
> Also I'd suggest an ordering like:
>
> + spi: spi at 20074000 {
> + compatible = "rockchip,rockchip-spi";
> + reg = <0x20074000 0x1000>;
> + interrupts = <GIC_SPI 23 IRQ_TYPE_LEVEL_HIGH>;
> + clocks =<&cru PCLK_SPI>, <&cru SCLK_SPI>;
> + clock-names = "apb-pclk","spi_pclk";
> + dmas = <&pdma 8>, <&pdma 9>;
> + dma-names = "tx", "rx";
> + num-cs = <2>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&spi_txd &spi_rxd &spi_clk &spi_cs0 &spi_cs1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + status = "disabled";
> + };
Okay, I will remove the cs1/num-cs in here.
Thanks.
-
Caesar
>
> Heiko
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
--
Thanks,
Caesar
next prev parent reply other threads:[~2016-02-01 6:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:43 [PATCH v4 0/9] Add the family patches to support for kylin board Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 8:43 ` [PATCH v4 1/9] ARM: dts: rockchip: add the leds control " Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-31 10:46 ` Heiko Stuebner
2016-01-31 10:46 ` Heiko Stuebner
2016-02-01 6:40 ` Caesar Wang
2016-02-01 6:40 ` Caesar Wang
2016-02-01 6:40 ` Caesar Wang
[not found] ` <1453970618-4383-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-01-28 8:43 ` [PATCH v4 2/9] ARM: dts: rockchip: add hdmi/vop device node for rk3036 Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-31 9:10 ` [PATCH v4.1 6/9] ASoC: rt5616: add mclk property for rt5616 document Caesar Wang
2016-01-31 9:10 ` Caesar Wang
[not found] ` <1454231443-22354-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-02-01 14:48 ` Rob Herring
2016-02-01 14:48 ` Rob Herring
2016-01-28 8:43 ` [PATCH v4 3/9] clk: rockchip: rk3036: fix and add node id for emac clock Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 8:43 ` [PATCH v4 4/9] ARM: dts: rockchip: add support emac for RK3036 Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 8:43 ` [PATCH v4 5/9] ARM: dts: rockchip: add mclk for rt5616 on kylin board Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 8:43 ` [PATCH v4 6/9] ASoC: rt5616: add mclk property for rt5616 document Caesar Wang
2016-01-29 16:28 ` Rob Herring
2016-01-31 9:09 ` Caesar Wang
2016-01-31 9:09 ` Caesar Wang
2016-01-28 8:43 ` [PATCH v4 7/9] ASoC: rt5616: trivial: fix the typo Caesar Wang
2016-01-28 8:43 ` Caesar Wang
2016-01-28 22:51 ` Applied "ASoC: rt5616: trivial: fix the typo" to the asoc tree Mark Brown
2016-01-28 8:43 ` [PATCH v4 8/9] ASoC: rt5616: add the mclk for the codec driver Caesar Wang
2016-01-28 22:51 ` Applied "ASoC: rt5616: add the mclk for the codec driver" to the asoc tree Mark Brown
2016-01-28 8:43 ` [PATCH v4 9/9] ARM: dts: rockchip: support the spi for rk3036 Caesar Wang
2016-01-28 8:43 ` Caesar Wang
[not found] ` <1453970618-4383-10-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-01-31 11:06 ` Heiko Stuebner
2016-01-31 11:06 ` Heiko Stuebner
2016-01-31 11:06 ` Heiko Stuebner
2016-02-01 6:32 ` Caesar Wang [this message]
2016-02-01 6:32 ` Caesar Wang
2016-02-01 7:30 ` [PATCH v4.1 " Caesar Wang
2016-02-01 7:30 ` Caesar Wang
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=56AEFC1B.60407@gmail.com \
--to=caesar.upstream@gmail.com \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jay.xu@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=keescook@google.com \
--cc=leozwang@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sonnyrao@chromium.org \
--cc=wxt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.