linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 1/4] rcar-phy: add R8A7778 support
Date: Tue, 16 Apr 2013 22:36:49 +0000	[thread overview]
Message-ID: <516DD281.2060402@cogentembedded.com> (raw)
In-Reply-To: <201304170132.43232.sergei.shtylyov@cogentembedded.com>

On 04/17/2013 01:32 AM, 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>
> Acked-by: Felipe Balbi <balbi@ti.com>
[...]
> @@ -109,10 +126,11 @@ static int rcar_usb_phy_init(struct usb_
>   			goto phy_init_end;
>   		}
>   
> -		/* (4) USB-PHY reset clear */
> +		/* (5) USB-PHY reset clear */
>   		iowrite32(PHY_ENB | PLL_ENB | PHY_RST, (reg0 + USBPCTRL1));
>   
>   		/* Board specific port settings */
> +		printk("sizeof(*pdata) = %d\n", sizeof(*pdata));

    Shoot! I thought I'd killed that... :-(

WBR, Sergei


      reply	other threads:[~2013-04-16 22:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 21:32 [PATCH v3 1/4] rcar-phy: add R8A7778 support Sergei Shtylyov
2013-04-16 22:36 ` 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=516DD281.2060402@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 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).