From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Petr Kulhavy <petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
Cc: balbi-l0cyMroinI0@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] Drivers: MUSB: Davinci MUSB: added DT support
Date: Thu, 21 Jan 2016 17:07:51 -0600 [thread overview]
Message-ID: <20160121230751.GA3991@rob-hp-laptop> (raw)
In-Reply-To: <1453387999-4485-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
On Thu, Jan 21, 2016 at 03:53:19PM +0100, Petr Kulhavy wrote:
> TI DaVinci MUSB driver equipped with DeviceTree support.
> Tested with AM1808 board and USB2.0 (OTG) in host mode.
>
> Signed-off-by: Petr Kulhavy <petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
> ---
> .../devicetree/bindings/usb/da8xx-usb.txt | 52 +++++++
> drivers/usb/musb/da8xx.c | 166 +++++++++++++++++++++
> include/linux/platform_data/usb-davinci.h | 3 +-
> 3 files changed, 220 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/usb/da8xx-usb.txt
>
> diff --git a/Documentation/devicetree/bindings/usb/da8xx-usb.txt b/Documentation/devicetree/bindings/usb/da8xx-usb.txt
> new file mode 100644
> index 0000000..c81d665
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/da8xx-usb.txt
Follow the compatible string for the filename (with wildcards is fine).
> @@ -0,0 +1,52 @@
> +TI DaVinci MUSB
> +
> +Required properties:
> +
> + - compatible : Should be "ti,da850-musb" or "ti,da830-musb"
> +
> + - mode : USB mode. "1" signifies HOST, "2" represents PERIPHERAL,
> + "3" represents OTG.
Surely we have a similar property defined already. Don't create
something new.
> +
> + - power : This signifies the maximum current the controller can
> + supply in host mode. The unit size is 2mA, the maximum value is 510mA.
You should model this as a regulator.
> + - num-eps : Specifies the number of endpoints. This is also a
> + MUSB configuration-specific setting.
Just spell out endpoints.
> +
> + - multipoint : Should be "1" indicating the musb controller supports
> + multipoint. This is a MUSB configuration-specific setting.
What does multipoint mean?
> + - ram-bits : Specifies the ram address size.
Needs a better description. Then it probably needs a better name too,
but without a description I can't tell what that would be.
> +
> +
> +Optional properties:
> +
> + - da8xx,phy20-clkmux-cfg: Integer. Defines the USB 2.0 PHY reference clock source.
> + Supported values: "0" for external pin, "1" for internal PLL.
How about a boolean property instead. Name it based on the less used
option (external pin I'm guessing).
> + - da8xx,phy20-refclock-frequency : Integer. Defines the USB 2.0 PHY reference clock input
> + frequency in Hz in case the clock is generated by the internal PLL.
> + Supported values are 12MHz, 13MHz, 19.2MHz, 20MHz, 24MHz, 26MHz, 38.4MHz, 40MHz, 48MHz
da8xx is not a vendor.
Rob
--
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:[~2016-01-21 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 14:53 [PATCH 2/2] Drivers: MUSB: Davinci MUSB: added DT support Petr Kulhavy
[not found] ` <1453387999-4485-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-01-21 18:05 ` Sergei Shtylyov
2016-01-21 23:07 ` Rob Herring [this message]
2016-01-22 9:01 ` Petr Kulhavy
2016-01-22 9:03 ` Petr Kulhavy
2016-01-24 19:00 ` Sergei Shtylyov
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=20160121230751.GA3991@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=petr-Qh/3xLP0EvwAvxtiuMwx3w@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