From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
SH-Linux <linux-sh@vger.kernel.org>,
kuninori morimoto <kuninori.morimoto.gx@renesas.com>,
Ulrich Hecht <ulrich.hecht@gmail.com>
Subject: Re: [PATCH v3 2/2] usb: renesas_usbhs: Add device tree support for R-Car H2 and M2
Date: Thu, 2 Oct 2014 09:05:11 +0900 [thread overview]
Message-ID: <542C96B7.4030407@renesas.com> (raw)
In-Reply-To: <542C547C.1080601@cogentembedded.com>
Hello.
(2014/10/02 4:22), Sergei Shtylyov wrote:
> On 10/01/2014 01:34 AM, Sergei Shtylyov wrote:
>
>>>>> This driver supports other SoCs, but they need boards/Soc depend code.
>>>>> So, this patch adds device tree support for R-Car H2 and M2 initially.
>
>>>>> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>>>>> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>>>>> ---
>>>>> drivers/usb/renesas_usbhs/common.c | 44
>>>>> ++++++++++++++++++++++++++++++++++++
>>>>> 1 file changed, 44 insertions(+)
>
>>>>> diff --git a/drivers/usb/renesas_usbhs/common.c
>>>>> b/drivers/usb/renesas_usbhs/common.c
>>>>> index 1b9bf8d..b3b6813 100644
>>>>> --- a/drivers/usb/renesas_usbhs/common.c
>>>>> +++ b/drivers/usb/renesas_usbhs/common.c
>> [...]
>>>>> @@ -438,6 +440,43 @@ static int usbhsc_drvcllbck_notify_hotplug(struct
>>>>> platform_device *pdev)
>>>> [...]
>>>>> +static struct renesas_usbhs_platform_info *usbhs_parse_dt(struct device
>>>>> *dev)
>>>>> +{
>>>>> + struct renesas_usbhs_platform_info *info;
>>>>> + struct renesas_usbhs_driver_param *dparam;
>>>>> + const struct of_device_id *of_id = of_match_device(usbhs_of_match, dev);
>>>>> + u32 tmp;
>>>>> + int gpio;
>>>>> +
>>>>> + info = devm_kzalloc(dev, sizeof(*info), GFP_KERNEL);
>>>>> + if (!info)
>>>>> + return NULL;
>>>>> +
>>>>> + dparam = &info->driver_param;
>>>>> + dparam->type = of_id ? (u32)of_id->data : 0;
>>>>> + if (!of_property_read_u32(dev->of_node, "renesas,buswait", &tmp))
>>>>> + dparam->buswait_bwait = tmp;
>>>>> + gpio = of_get_named_gpio_flags(dev->of_node, "renesas,enable-gpio", 0,
>>>>> + NULL);
>>>>> + if (gpio > 0)
>>>>> + dparam->enable_gpio = gpio;
>>>>> +
>>>>> + return info;
>
>>>> I don't see where you parse the optional "phy" property. It should exist
>>>> for the Lager and Koelsch boards you target.
>
> [...]
>
>>> About using the phy driver in renesas_usbhs driver, I intend to modify
>>> the drivers/usb/renesas_usbhs/rcar.c.
>
>> Hm, it slready supports 'struct usb_phy'. Also PHYs are not limited to
>> R-Car Gen2 SoCs...
>
> OK, let's do this locally to rcar2.c for now. But since you still haven't
> provided the patches and I'm tasked with the USBHS support, I have to take the
> further development in my hands.
Thank you for the reply. And, I'm sorry for the deleyed response.
I will submit the patches (add support generic phy in rcar.c and device node
for some SoCs) today.
Best regards,
Yoshihiro Shimoda
>>> Best regards,
>>> Yoshihiro Shimoda
>
> WBR, Sergei
>
prev parent reply other threads:[~2014-10-02 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 5:25 [PATCH v3 2/2] usb: renesas_usbhs: Add device tree support for R-Car H2 and M2 Yoshihiro Shimoda
[not found] ` <5406A664.2050501-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2014-09-29 16:35 ` Sergei Shtylyov
2014-09-30 9:51 ` Yoshihiro Shimoda
[not found] ` <542A7D29.3010805-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2014-09-30 21:34 ` Sergei Shtylyov
[not found] ` <542B21DE.4010903-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-10-01 19:22 ` Sergei Shtylyov
2014-10-02 0:05 ` Yoshihiro Shimoda [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=542C96B7.4030407@renesas.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ulrich.hecht@gmail.com \
/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).