From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Samsung 2nd DT updates for v3.15
Date: Wed, 02 Apr 2014 13:29:04 +0900 [thread overview]
Message-ID: <012501cf4e2c$149943f0$3dcbcbd0$@samsung.com> (raw)
In-Reply-To: <201403290253.14497.arnd@arndb.de>
Arnd Bergmann wrote:
>
[...]
> >
> > .../devicetree/bindings/ata/exynos-sata-phy.txt | 14 ---------
> > .../devicetree/bindings/ata/exynos-sata.txt | 25
+++++++++------
> > .../devicetree/bindings/phy/samsung-phy.txt | 36
> > ++++++++++++++++++++++
>
> Looking through the branch contents, I noticed that the examples in the
> bindings contain mandatory properties that are not documented.
>
Oops, sorry.
> I have merged your branch into next/cleanup3 of the arm-soc tree,
> but I also applied a patch on top to document the missing strings
> and properties. It is currently the top commit on the branch, so
> if anyone spots a mistake, we can probably rectify it.
>
Thanks a lot :-)
> Please be more careful with binding documentation in the future.
> Was this actually reviewed on the devicetree-discuss mailing list?
>
Sure.
- Kukjin
> Arnd
>
> 9<-----
> From 9dfbff16b422a4bac7ad309847c7bc5d65653392 Mon Sep 17 00:00:00 2001
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Sat, 29 Mar 2014 02:15:43 +0100
> Subject: [PATCH] devicetree: fix newly added exynos sata bindings
>
> Commit ba0d7ed391b7b "ARM: dts: enable ahci sata and sata phy for
> exynos5250" added a new binding document for the sata phy device,
> and changed the sata controller binding. However, in both cases
> significant aspects of the binding remained undocumented.
> This attempts to reconstruct the actual binding from the usage.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Cc: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>
> Cc: Kishon Vijay Abraham I <kishon@ti.com>
> Cc: Kukjin Kim <kgene.kim@samsung.com>
>
> diff --git a/Documentation/devicetree/bindings/ata/exynos-sata.txt
> b/Documentation/devicetree/bindings/ata/exynos-sata.txt
> index b2adb1f..cb48448 100644
> --- a/Documentation/devicetree/bindings/ata/exynos-sata.txt
> +++ b/Documentation/devicetree/bindings/ata/exynos-sata.txt
> @@ -8,8 +8,14 @@ Required properties:
> - interrupts : <interrupt mapping for SATA IRQ>
> - reg : <registers mapping>
> - samsung,sata-freq : <frequency in MHz>
> -- phys : as mentioned in phy-bindings.txt
> -- phy-names : as mentioned in phy-bindings.txt
> +- phys : Must contain exactly one entry as
specified
> + in phy-bindings.txt
> +- phy-names : Must be "sata-phy"
> +
> +Optional properties:
> +- clocks : Must contain an entry for each entry in
clock-names.
> +- clock-names : Shall be "sata" for the external SATA bus
> clock,
> + and "sclk_sata" for the internal controller clock.
>
> Example:
> sata at 122f0000 {
> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
> b/Documentation/devicetree/bindings/phy/samsung-phy.txt
> index a937f75..67d38b3 100644
> --- a/Documentation/devicetree/bindings/phy/samsung-phy.txt
> +++ b/Documentation/devicetree/bindings/phy/samsung-phy.txt
> @@ -30,7 +30,11 @@ Each SATA PHY controller should have its own node.
> Required properties:
> - compatible : compatible list, contains "samsung,exynos5250-sata-
> phy"
> - reg : offset and length of the SATA PHY register set;
> -- #phy-cells : from the generic phy bindings;
> +- #phy-cells : must be zero
> +- clocks : must be exactly one entry
> +- clock-names : must be "sata_phyctrl"
> +- samsung,exynos-sataphy-i2c-phandle : a phandle to the I2C device, no
> arguments
> +- samsung,syscon-phandle : a phandle to the PMU system controller, no
> arguments
>
> Example:
> sata_phy: sata-phy at 12170000 {
prev parent reply other threads:[~2014-04-02 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 14:13 [GIT PULL 2/2] Samsung 2nd DT updates for v3.15 Kukjin Kim
2014-03-29 1:53 ` Arnd Bergmann
2014-04-02 4:29 ` Kukjin Kim [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='012501cf4e2c$149943f0$3dcbcbd0$@samsung.com' \
--to=kgene.kim@samsung.com \
--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).