From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>
Cc: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 2/3] usb: gadget: pxa27x_udc device-tree documentation
Date: Mon, 30 Jun 2014 09:49:13 +0100 [thread overview]
Message-ID: <20140630084913.GO7262@leverpostej> (raw)
In-Reply-To: <87fviooygi.fsf-GANU6spQydw@public.gmane.org>
On Sun, Jun 29, 2014 at 10:29:49AM +0100, Robert Jarzmik wrote:
> Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> writes:
>
> > On Wed, Jun 25, 2014 at 08:54:01PM +0100, Robert Jarzmik wrote:
> >> > The name of the clock input doesn't make sense.
> >> I don't understand. With [1] does it make any more sense ? If not you'll have to
> >> expand a bit more the "doesn't make sense".
> >
> > My concern is that clock-names is supposed to describe the name of the
> > input clock line from the view of the IP block. "pxa27x-udc" doesn't
> > sound like the name of a clock input line from the view of the UDC
> > block.
> >
> > I assume the clock input line you care about has a more specific name
> > than "pxa27x-udc"?
> Not as far as I know. The technical reference manual call it "udc clock", so
> it's even "less" specific ...
Not from the point of view of the device. The clock-names are namespaced
to the particular binding, so they're equally specific.
Given the above I'd recommend naming the clock "udc" or "udc_clk". That
doesn't pretend to be overly specific, and matches the TRM.
> Marvell engineers have probably the internal schematics and the name of the
> clock, but outsiders like me only have "udc" ...
Sure, not having the full specs is always a pain.
Mark.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-30 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 9:04 [PATCH v2 1/3] usb: gadget: pxa27x_udc: add devicetree support Robert Jarzmik
[not found] ` <1403427899-32154-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2014-06-22 9:04 ` [PATCH v2 2/3] usb: gadget: pxa27x_udc device-tree documentation Robert Jarzmik
[not found] ` <1403427899-32154-2-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2014-06-25 10:33 ` Mark Rutland
2014-06-25 19:54 ` Robert Jarzmik
[not found] ` <87zjh07okm.fsf-GANU6spQydw@public.gmane.org>
2014-06-26 8:59 ` Mark Rutland
2014-06-29 9:29 ` Robert Jarzmik
[not found] ` <87fviooygi.fsf-GANU6spQydw@public.gmane.org>
2014-06-30 8:49 ` Mark Rutland [this message]
2014-06-25 10:41 ` [PATCH v2 1/3] usb: gadget: pxa27x_udc: add devicetree support Mark Rutland
2014-06-25 20:03 ` Robert Jarzmik
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=20140630084913.GO7262@leverpostej \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robert.jarzmik-GANU6spQydw@public.gmane.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