From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 1/4] rcar-phy: add R8A7778 support
Date: Mon, 15 Apr 2013 11:42:33 +0000 [thread overview]
Message-ID: <516BE7A9.6080104@cogentembedded.com> (raw)
In-Reply-To: <201304130340.15019.sergei.shtylyov@cogentembedded.com>
Hello.
On 13-04-2013 3:40, I wrote:
> The driver currently only supports R8A7779 SoC. Compared to it, R8A7778 USB-PHY
> has extra register range containing two high-speed signal quality characteristic
> control registers which should be set up during USB-PHY startup depending on
> whether a ferrite bead is in use or not. So, we now handle an optional second
> memory range in the driver's probe method, add the 'ferrite_bead' field to the
> driver's platform data, and add an extra (optional) step to the USB-PHY startup
> routine which sets up the extended registers.
>
> Also mark in the driver's Kconfig section that R8A7778 is now supported and
> generally clarify that section, uppercasing the word "phy", while at it...
>
> The patch has been tested on the Marzen and BOCK-W boards.
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
[...]
> Index: renesas/include/linux/usb/rcar-phy.h
> =================================> --- renesas.orig/include/linux/usb/rcar-phy.h
> +++ renesas/include/linux/usb/rcar-phy.h
> @@ -21,6 +21,7 @@ struct rcar_phy_platform_data {
> bool active_high:1; /* true: active high, false: active low */
> /* Set to true on port 1 in function mode */
> } ovc_pin[3];
> + bool ferrite_bead:1; /* (R8A7778 only) */
I think I'll repost this series. I want to move thjis field to the start
of structure for better packing, and add a comment to 'ovc_pin'.
I've also forgotten to add an ACK by Felipe.
WBR, Sergei
prev parent reply other threads:[~2013-04-15 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 23:40 [PATCH v2 1/4] rcar-phy: add R8A7778 support Sergei Shtylyov
2013-04-15 11:42 ` Sergei Shtylyov [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=516BE7A9.6080104@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.