From: Mark Rutland <mark.rutland@arm.com>
To: Brent Wang <wangbintian@gmail.com>
Cc: "dan.zhao@hisilicon.com" <dan.zhao@hisilicon.com>,
"btw@mail.itp.ac.cn" <btw@mail.itp.ac.cn>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"wangbinghui@hisilicon.com" <wangbinghui@hisilicon.com>,
Will Deacon <Will.Deacon@arm.com>,
"huxinwei@huawei.com" <huxinwei@huawei.com>,
"khilman@linaro.org" <khilman@linaro.org>,
"haojian.zhuang@linaro.org" <haojian.zhuang@linaro.org>,
"yanhaifeng@gmail.com" <yanhaifeng@gmail.com>,
"rob.herring@linaro.org" <rob.herring@linaro.org>,
"mturquette@linaro.org" <mturquette@linaro.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"khilman@kernel.org" <khilman@kernel.org>,
"xuwei5@hisilicon.com" <xuwei5@hisilicon.com>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>,
"sledge.yanwei@huawei.com" <sledge.yanwei@huawei.com>,
"kong.kongxinwei@hisilicon.com" <kong.kongxinwei@hisilicon.com>,
"heyunlei@huawei.com" <heyunlei@huawei.com>,
"w.f@huawei.com" <w.f>
Subject: Re: [PATCH v4 5/5] arm64: dts: Add dts files for Hisilicon Hi6220 SoC
Date: Wed, 6 May 2015 17:23:01 +0100 [thread overview]
Message-ID: <20150506162301.GD2974@leverpostej> (raw)
In-Reply-To: <CAAS=xmjf+WYeZe7jPqVK26QWsv3tPqgdiy1TNUty6qWzZcsMkA@mail.gmail.com>
On Wed, May 06, 2015 at 05:03:29PM +0100, Brent Wang wrote:
> Hi Mark,
>
> 2015-05-06 23:44 GMT+08:00, Mark Rutland <mark.rutland@arm.com>:
> > Hi,
> >
> >> How about add the following binding rule to my 2/5 patch:
> >> ---------------------------
> >> *Hisilicon Enhanced ARM AMBA Primecell PL011 serial UART
> >>
> >> Required properties:
> >> - compatible: must be "hisilicon,hi6220-uart", "arm,primecell",
> >> "arm,pl011"
> >
> > "arm,primecell" should come last.
> >
> >> - reg: exactly one register range with length 0x1000
> >> - interrupts: exactly one interrupt specifier
> >>
> >> See also bindings/serial/pl011.txt
> >>
> >> Example:
> >>
> >> uart0: uart@f8015000 {
> >> compatible = "hisilicon,hi6220-uart", "arm,pl011",
> >> "arm,primecell";
> >> reg = <0x0 0xf8015000 0x0 0x1000>;
> >> interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>;
> >> clocks = <&ao_ctrl HI6220_UART0_PCLK>, <&ao_ctrl
> >> HI6220_UART0_PCLK>;
> >> clock-names = "uartclk", "apb_pclk";
> >> };
> >
> > How about for the moment we just modify the existing pl011 binding
> > document to allow for the hi6220-specific string in addition to its
> > existing strings? We can always split it out later if the hi6220 UART
> > binding needs to be significantly divergent.
> How about adding the following rule to pl011.txt?
> ----------
> diff --git a/Documentation/devicetree/bindings/serial/pl011.txt
> b/Documentation/devicetree/bindings/serial/pl011.txt
> index ba3ecb8..1221ccb 100644
> --- a/Documentation/devicetree/bindings/serial/pl011.txt
> +++ b/Documentation/devicetree/bindings/serial/pl011.txt
> @@ -35,6 +35,10 @@ Optional properties:
> - poll-timeout-ms:
> Poll timeout when auto-poll is set, default
> 3000ms.
> +- compatible: "hisilicon,hi6220-uart":
> + Hisilicon does some enhancements (e.g. larger FIFO length)
> + based on PL011, so when using these UART hosts, this compatible
> + string should be added.
Up at the top of the document there's already a description of the
compatible property. Just change it into a list something like:
- compatible: should contain one of the following sequences:
* "arm,pl011", "arm,primecell"
* "hisilicon,hi6220-pl011", "arm,pl011", "arm,primecell"
> See also bindings/arm/primecell.txt
> ------------
> >
> >> > Is UART 0 different from UART1 and UART2?
> >> Yes, but my patch just includes UART0, we do some changements for
> >> UART1/2
> >> to improve performance.
> >
> > Sure, but we need to make sure we can choose a sane compatible string
> > for them, that won't clash with whatever we choose for UART0.
> OK, do I also need to add compatible ""hisilicon,hi6220-uart"," to UART0 node?
This depends on a number of factors. Questions below.
> > Are they the same IP as UART0, or fundamentally different?
> The same IP.
> >
> > Are they also PL011 derived?
> Yes, just do some enhancements to improve performance.
What exactly is different between UART0 and UART{1,2}, given they are
the same IP?
Can UART{1,2} be used as if they are standard PL011 instances?
Is the difference internal, or do they just have different
clocks/regulators/etc?
Do they have feature control pins tied off differently?
Are they simply programmed differently at reset by firmware?
Thanks,
Mark.
next prev parent reply other threads:[~2015-05-06 16:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 12:06 [PATCH v4 0/5] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
2015-05-05 12:06 ` [PATCH v4 2/5] arm64: hi6220: Document devicetree bindings for Hisilicon hi6220 SoC Bintian Wang
2015-05-15 0:27 ` Stephen Boyd
[not found] ` <20150515002739.GF31753-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-05-15 1:31 ` Bintian
[not found] ` <1430827599-11560-1-git-send-email-bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-05-05 12:06 ` [PATCH v4 1/5] arm64: Enable Hisilicon ARMv8 SoC family in Kconfig and defconfig Bintian Wang
2015-05-05 12:06 ` [PATCH v4 3/5] clk: hi6220: Document devicetree bindings for hi6220 clock Bintian Wang
2015-05-15 0:26 ` Stephen Boyd
2015-05-05 12:06 ` [PATCH v4 4/5] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
2015-05-15 0:25 ` Stephen Boyd
2015-05-15 7:42 ` Bintian
2015-05-15 19:30 ` Stephen Boyd
2015-05-16 2:54 ` Brent Wang
2015-05-19 20:35 ` Stephen Boyd
[not found] ` <555B9E7B.9000809-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-05-20 0:52 ` Bintian
2015-05-05 12:06 ` [PATCH v4 5/5] arm64: dts: Add dts files for Hisilicon Hi6220 SoC Bintian Wang
2015-05-05 17:13 ` Mark Rutland
2015-05-06 3:16 ` Bintian
2015-05-06 3:51 ` Leo Yan
2015-05-06 9:20 ` Mark Rutland
2015-05-06 11:17 ` Leo Yan
2015-05-06 6:50 ` Bintian
2015-05-06 9:30 ` Mark Rutland
2015-05-06 10:36 ` Bintian
2015-05-06 10:55 ` Mark Rutland
2015-05-06 15:31 ` Brent Wang
2015-05-06 15:44 ` Mark Rutland
2015-05-06 16:03 ` Brent Wang
2015-05-06 16:23 ` Mark Rutland [this message]
2015-05-06 17:15 ` Brent Wang
2015-05-07 7:24 ` Bintian
2015-05-13 7:12 ` Bintian Wang
2015-05-13 7:30 ` Bintian
2015-05-06 10:38 ` Haojian Zhuang
2015-05-06 11:01 ` Mark Rutland
2015-05-05 13:45 ` [PATCH v4 0/5] arm64,hi6220: Enable " Haojian Zhuang
2015-05-13 7:33 ` Bintian
2015-05-13 9:16 ` Will Deacon
2015-05-13 9:19 ` Arnd Bergmann
2015-05-13 10:17 ` Bintian
2015-05-05 23:46 ` Tyler Baker
2015-05-06 10:46 ` Bintian
2015-05-07 9:02 ` Will Deacon
2015-05-07 9:29 ` Bintian
2015-05-07 11:25 ` Will Deacon
2015-05-07 11:55 ` Leo Yan
2015-05-07 12:01 ` Bintian
2015-05-07 12:57 ` Will Deacon
2015-05-07 13:06 ` Bintian
2015-05-07 9:33 ` Haojian Zhuang
2015-05-07 10:44 ` Jorge Ramirez-Ortiz
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=20150506162301.GD2974@leverpostej \
--to=mark.rutland@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=btw@mail.itp.ac.cn \
--cc=dan.zhao@hisilicon.com \
--cc=haojian.zhuang@linaro.org \
--cc=heyunlei@huawei.com \
--cc=huxinwei@huawei.com \
--cc=jh80.chung@samsung.com \
--cc=khilman@kernel.org \
--cc=khilman@linaro.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=mturquette@linaro.org \
--cc=rob.herring@linaro.org \
--cc=sledge.yanwei@huawei.com \
--cc=wangbinghui@hisilicon.com \
--cc=wangbintian@gmail.com \
--cc=xuwei5@hisilicon.com \
--cc=yanhaifeng@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).