From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] phy: add combo phy driver for HiSilicon STB SoCs
Date: Tue, 24 Oct 2017 14:41:09 +0800 [thread overview]
Message-ID: <20171024064108.GC6403@dragon> (raw)
In-Reply-To: <20171023222850.ecavz6jm2mnoplea@rob-hp-laptop>
Hi Rob,
On Mon, Oct 23, 2017 at 05:28:50PM -0500, Rob Herring wrote:
> On Sun, Oct 15, 2017 at 12:48:02PM +0800, Shawn Guo wrote:
> > From: Jianguo Sun <sunjianguo1@huawei.com>
> >
> > Add combo phy driver for HiSilicon STB SoCs. This phy can be
> > used as pcie-phy, sata-phy or usb-phy.
> >
> > Signed-off-by: Jianguo Sun <sunjianguo1@huawei.com>
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > .../bindings/phy/phy-hi3798cv200-combphy.txt | 21 ++
>
> Please split bindings to separate patch especially for new ones.
Yeah, have already done that in v2 [1].
> > drivers/phy/Makefile | 1 +
> > drivers/phy/hisilicon/Kconfig | 9 +
> > drivers/phy/hisilicon/Makefile | 1 +
> > drivers/phy/hisilicon/phy-histb-combphy.c | 236 +++++++++++++++++++++
> > 5 files changed, 268 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/phy/phy-hi3798cv200-combphy.txt
> > create mode 100644 drivers/phy/hisilicon/phy-histb-combphy.c
> >
> > diff --git a/Documentation/devicetree/bindings/phy/phy-hi3798cv200-combphy.txt b/Documentation/devicetree/bindings/phy/phy-hi3798cv200-combphy.txt
> > new file mode 100644
> > index 000000000000..c7121cdcaed9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/phy/phy-hi3798cv200-combphy.txt
> > @@ -0,0 +1,21 @@
> > +HiSilicon STB PCIE/SATA/USB3 PHY
> > +
> > +Properties:
> > +- compatible: Should be "hisilicon,hi3798cv200-combphy"
> > +- #phy-cells: Should be 1. The cell number is used to select the phy mode:
> > + 0: PCIe mode
> > + 1: USB 3.0 mode
> > + 2: SATA mode
> > +- clocks: The phandle to clock provider and clock specifier pair.
> > +- resets: The phandle to reset controller and reset specifier pair.
> > +- hisilicon,peripheral-syscon: The phandle to the peripheral controller.
>
> Could just be a child of the syscon instead?
It should be doable, but I do not fully understand the benefits of doing
that.
Shawn
[1] https://www.spinics.net/lists/devicetree/msg199804.html
next prev parent reply other threads:[~2017-10-24 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 4:48 [PATCH] phy: add combo phy driver for HiSilicon STB SoCs Shawn Guo
2017-10-18 12:43 ` Kishon Vijay Abraham I
2017-10-23 1:55 ` Shawn Guo
2017-10-23 22:28 ` Rob Herring
2017-10-24 6:41 ` Shawn Guo [this message]
2017-10-24 15:12 ` Shawn Guo
2017-10-25 13:34 ` Rob Herring
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=20171024064108.GC6403@dragon \
--to=shawnguo@kernel.org \
--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).