From: Lee Jones <lee.jones@linaro.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"DCG_UPD_stlinux_kernel@list.st.com"
<DCG_UPD_stlinux_kernel@list.st.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@st.com>
Subject: Re: [PATCH v2 1/3] ata: ahci_st: Provide DT bindings for ST's SATA implementation
Date: Wed, 12 Mar 2014 12:48:35 +0000 [thread overview]
Message-ID: <20140312124835.GA22450@lee--X1> (raw)
In-Reply-To: <20140312114257.GA17461@e106331-lin.cambridge.arm.com>
> > +This binding describes a SATA device.
> > +
> > +Required properties:
> > + - compatible : Must be "st,ahci"
>
> Is there not a more specific name? This is awfully generic.
There isn't one. ST only have one AHCI driver. The driver is named as
generically.
> > + - reg : Physical base addresses and length of register sets
> > + - interrupts : Interrupt associated with the SATA device
> > + - interrupt-names : Associated name must be; "hostc"
> > + - resets : The power-down and soft-reset lines of SATA IP
> > + - reset-names : Associated names must be; "pwr-dwn" and "sw-rst"
>
> Get rid of the semicolon, it makes this harder to read. Same for the
> other -names proeprties.
Sure.
> > + - clocks : The phandle for the clock
> > + - clock-names : Associated name must be; "ahci_clk"
> > + - phys : The phandle for the PHY device
> > + - phy-names : Associated name must be; "ahci_phy"
>
> This looks sane, but I'd like to see a more specific description and
> compatible string.
Specific description in what sense?
"This binding describes a SATA device."
to
"This binding describes ST's SATA device." ?
> > +Example:
> > +
> > + sata0: sata@fe380000 {
> > + compatible = "st,ahci";
> > + reg = <0xfe380000 0x1000>;
> > + interrupts = <GIC_SPI 157 IRQ_TYPE_NONE>;
> > + interrupt-names = "hostc";
> > + phys = <&miphy365x_phy MIPHY_PORT_0 MIPHY_TYPE_SATA>;
> > + phy-names = "ahci_phy";
> > + resets = <&powerdown STIH416_SATA0_POWERDOWN>,
> > + <&softreset STIH416_SATA0_SOFTRESET>;
> > + reset-names = "pwr-dwn", "sw-rst";
> > + clocks = <&CLK_S_ICN_REG_0>;
> > + clock-names = "ahci_clk";
> > + };
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-03-12 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 11:41 [PATCH v2 1/3] ata: ahci_st: Provide DT bindings for ST's SATA implementation Lee Jones
2014-02-25 11:41 ` [PATCH v2 2/3] ARM: DT: STi: Add DT node for ST's SATA device Lee Jones
[not found] ` <1393328481-7251-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-03-12 11:42 ` [PATCH v2 1/3] ata: ahci_st: Provide DT bindings for ST's SATA implementation Mark Rutland
2014-03-12 12:48 ` Lee Jones [this message]
2014-03-12 16:06 ` Arnd Bergmann
2014-03-12 17:14 ` Lee Jones
2014-03-12 18:59 ` Arnd Bergmann
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=20140312124835.GA22450@lee--X1 \
--to=lee.jones@linaro.org \
--cc=DCG_UPD_stlinux_kernel@list.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=srinivas.kandagatla@st.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).