From: Mark Rutland <mark.rutland@arm.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Stanimir Varbanov <svarbanov@mm-sol.com>,
"balbi@ti.com" <balbi@ti.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"rob@landley.net" <rob@landley.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"idos@codeaurora.org" <idos@codeaurora.org>,
"mgautam@codeaurora.org" <mgautam@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v6 2/3] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DW PHY's
Date: Tue, 22 Oct 2013 15:32:43 +0100 [thread overview]
Message-ID: <20131022143242.GA4691@kartoffel> (raw)
In-Reply-To: <1381246952.24031.83.camel@iivanov-dev.int.mm-sol.com>
[...]
> > > + phy->sleep_a_clk = devm_clk_get(phy->dev, "sleep_a");
> >
> > What means the "_a" in clock name?
>
> They are 2 PHY's on 8074 chip. This drivers is supposed to
> operate on PHY 0, thus sleep_a. PHY 1 is using sleep_b. Take a look
> here http://www.spinics.net/lists/arm-kernel/msg276945.html
When you say two PHYs, do you mean the HS PHY and the SS PHY?
Or are there two HS PHYs? If so, would the other HS PHY have a sleep_b clock?
The clock-names property should describe the clocks from the view of the device
itself. As we're describing the PHY in isolation, rather than a big block that
contains the PHY, the presesnce or absence of other PHYs should not affect the
name. If the "_a" suffix is only to differentiate the instance of PHY, it
should be dropped.
Thanks,
Mark.
next prev parent reply other threads:[~2013-10-22 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 7:44 [PATCH v6 0/3] DWC3 USB support for Qualcomm platform Ivan T. Ivanov
[not found] ` <1381131897-13910-1-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2013-10-07 7:44 ` [PATCH v6 1/3] usb: dwc3: msm: Add device tree binding information Ivan T. Ivanov
2013-10-07 7:44 ` [PATCH v6 2/3] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DW PHY's Ivan T. Ivanov
2013-10-07 9:22 ` Stanimir Varbanov
2013-10-08 15:42 ` Ivan T. Ivanov
2013-10-22 14:32 ` Mark Rutland [this message]
2013-10-22 15:39 ` Ivan T. Ivanov
2013-10-07 7:44 ` [PATCH v6 3/3] usb: dwc3: Add Qualcomm DWC3 glue layer driver Ivan T. Ivanov
2013-10-07 9:28 ` Stanimir Varbanov
2013-10-08 15:43 ` Ivan T. Ivanov
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=20131022143242.GA4691@kartoffel \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ian.campbell@citrix.com \
--cc=idos@codeaurora.org \
--cc=iivanov@mm-sol.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=svarbanov@mm-sol.com \
--cc=swarren@wwwdotorg.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).