From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Sugar Zhang <sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
Liang Chen <cl-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v1 2/2] arm64: dts: rk3328: add pdm node
Date: Sat, 17 Jun 2017 20:05:53 +0200 [thread overview]
Message-ID: <8940631.X8XUXX2eL4@phil> (raw)
In-Reply-To: <1497338867-52684-3-git-send-email-sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Hi,
Am Dienstag, 13. Juni 2017, 15:27:47 CEST schrieb Sugar Zhang:
> This patch add pdm controller device node for rk3328.
>
> Signed-off-by: Sugar Zhang <sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
please make the subject
"arm64: dts: rockchip: add rk3328 pdm node"
>
> ---
>
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 55 ++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index 7e69f1f..2435044 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -156,6 +156,25 @@
> clock-output-names = "xin24m";
> };
>
> + pdm: pdm@ff040000 {
> + compatible = "rockchip,pdm";
> + reg = <0x0 0xff040000 0x0 0x1000>;
> + clocks = <&cru SCLK_PDM>, <&cru HCLK_PDM>;
> + clock-names = "pdm_clk", "pdm_hclk";
> + dmas = <&dmac 16>;
> + #dma-cells = <1>;
please drop #dma-cells, this is not a dma-controller and only
a dma-client. #dma-cells is a property of dma-controllers.
> + dma-names = "rx";
> + pinctrl-names = "default", "sleep";
> + pinctrl-0 = <&pdmm0_clk
> + &pdmm0_fsync
> + &pdmm0_sdi0
> + &pdmm0_sdi1
> + &pdmm0_sdi2
> + &pdmm0_sdi3>;
> + pinctrl-1 = <&pdmm0_sleep>;
pinctrl doesn't match up. default pins are all separate, sleep pins are
all in one entry. So what is the use-case for the pins being separate?
I guess you always need clk, fsync and then one or more of the sdiX pins?
Can these be used independently [like sdi2 only] or is it something like
sdio pins and one of {1}, {1,2,3,4} or so?
So in general the groupings should match for all pinctrl states, because
if you for example do not use sdi3 and reuse it as gpio or so the sleep
pinctrl state would fail, as there would be conflict then.
Heiko
> + status = "disabled";
> + };
> +
> grf: syscon@ff100000 {
> compatible = "rockchip,rk3328-grf", "syscon", "simple-mfd";
> reg = <0x0 0xff100000 0x0 0x1000>;
> @@ -701,6 +720,42 @@
> };
> };
>
> + pdm-0 {
> + pdmm0_clk: pdmm0-clk {
> + rockchip,pins = <2 RK_PC2 2 &pcfg_pull_none>;
> + };
> +
> + pdmm0_fsync: pdmm0-fsync {
> + rockchip,pins = <2 RK_PC7 2 &pcfg_pull_none>;
> + };
> +
> + pdmm0_sdi0: pdmm0-sdi0 {
> + rockchip,pins = <2 RK_PC3 2 &pcfg_pull_none>;
> + };
> +
> + pdmm0_sdi1: pdmm0-sdi1 {
> + rockchip,pins = <2 RK_PC4 2 &pcfg_pull_none>;
> + };
> +
> + pdmm0_sdi2: pdmm0-sdi2 {
> + rockchip,pins = <2 RK_PC5 2 &pcfg_pull_none>;
> + };
> +
> + pdmm0_sdi3: pdmm0-sdi3 {
> + rockchip,pins = <2 RK_PC6 2 &pcfg_pull_none>;
> + };
> +
> + pdmm0_sleep: pdmm0-sleep {
> + rockchip,pins =
> + <2 RK_PC2 RK_FUNC_GPIO &pcfg_input_high>,
> + <2 RK_PC3 RK_FUNC_GPIO &pcfg_input_high>,
> + <2 RK_PC4 RK_FUNC_GPIO &pcfg_input_high>,
> + <2 RK_PC5 RK_FUNC_GPIO &pcfg_input_high>,
> + <2 RK_PC6 RK_FUNC_GPIO &pcfg_input_high>,
> + <2 RK_PC7 RK_FUNC_GPIO &pcfg_input_high>;
> + };
> + };
> +
> i2s1 {
> i2s1_mclk: i2s1-mclk {
> rockchip,pins = <2 RK_PB7 1 &pcfg_pull_none>;
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-06-17 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 7:27 [PATCH v1 0/2] Patches to add support pdm controller for rk3328 Sugar Zhang
2017-06-13 7:27 ` [PATCH v1 1/2] ASoC: rockchip: add support for pdm controller Sugar Zhang
2017-06-13 21:09 ` Applied "ASoC: rockchip: add support for pdm controller" to the asoc tree Mark Brown
2017-06-18 14:05 ` [PATCH v1 1/2] ASoC: rockchip: add support for pdm controller Rob Herring
2017-06-13 7:27 ` [PATCH v1 2/2] arm64: dts: rk3328: add pdm node Sugar Zhang
[not found] ` <1497338867-52684-3-git-send-email-sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-06-17 18:05 ` Heiko Stuebner [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=8940631.X8XUXX2eL4@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=cl-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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).