All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v6 9/9] rcar-phy: handle platform data
Date: Tue, 30 Apr 2013 19:02:18 +0000	[thread overview]
Message-ID: <5180153A.1090009@cogentembedded.com> (raw)
In-Reply-To: <201304231942.08507.sergei.shtylyov@cogentembedded.com>

Hello.

On 04/30/2013 02:42 PM, Felipe Balbi wrote:

>
>> Set the USBPCTRL0 register from the passed platform data in rcar_usb_phy_init();
>> don't reset it to 0 in  rcar_usb_phy_shutdown()  anymore as that does not make
>> sense.  Also, don't allow the driver's probe to succeed when the platform data
>> are not supplied with a device.
>>
>> The patch has been tested on the Marzen and BOCK-W boards.
>>
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>> Acked-by: Simon Horman <horms+renesas@verge.net.au>
> Acked-by: Felipe Balbi <balbi@ti.com>
>
>> Index: renesas/drivers/usb/phy/rcar-phy.c
>> =================================>> --- renesas.orig/drivers/usb/phy/rcar-phy.c
>> +++ renesas/drivers/usb/phy/rcar-phy.c
>> @@ -11,10 +12,11 @@
>>   
>>   #include <linux/delay.h>
>>   #include <linux/io.h>
>> -#include <linux/usb/otg.h>
>>   #include <linux/platform_device.h>
>>   #include <linux/spinlock.h>
>>   #include <linux/module.h>
>> +#include <linux/usb/otg.h>
> trailing change here.

    What do you mean by "trailing"? I just naturally grouped together 
headers from the same directory.

>   Please just mention it on the commit log. It doesn't a patch of its own :-p

    I'll drop it now probably as you told me to switch to 
include/linux/platfrom_data/...

>
>> @@ -89,8 +112,21 @@ static int rcar_usb_phy_init(struct usb_
>>   		/* (4) USB-PHY reset clear */
>>   		iowrite32(PHY_ENB | PLL_ENB | PHY_RST, (reg0 + USBPCTRL1));
>>   
>> -		/* set platform specific port settings */
>> -		iowrite32(0x00000000, (reg0 + USBPCTRL0));
>> +		/* Board specific port settings */
>> +		val = 0;
>> +		if (pdata->port1_func)
>> +			val |= PORT1;
>> +		if (pdata->penc1)
>> +			val |= PENC;
>> +		for (i = 0; i < 3; i++) {
>> +			/* OVCn bits follow each other in the right order */
>> +			if (pdata->ovc_pin[i].select_3_3v)
>> +				val |= OVC0 << i;
>> +			/* OVCn_ACT bits are spaced by irregular intervals */
>> +			if (pdata->ovc_pin[i].active_high)
>> +				val |= ovcn_act[i];
>> +		}
>> +		iowrite32(val, (reg0 + USBPCTRL0));
> not all architectures provide iowrite32(). Please make sure your driver
> builds on x86 and ARM by using SHOW_ALL_DRIVERS (on Kconfig).

    Sure, it builds on ARM because it was designed for ARM SH Mobile 
subarch.
I'll check x86 just in case.

> BTW, conversion away from iowrite32() could (should) be part of a
> separate patch. No need to prevent this one from being applied.
>

    Of course. You mean conversion to plain writel(), right?

WBR, Sergei


  parent reply	other threads:[~2013-04-30 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 15:42 [PATCH v6 9/9] rcar-phy: handle platform data Sergei Shtylyov
2013-04-30 10:42 ` Felipe Balbi
2013-04-30 19:02 ` Sergei Shtylyov [this message]
2013-05-15 14:01 ` Felipe Balbi
2013-05-15 14:05 ` 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=5180153A.1090009@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.