From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: Renesas RCar device-tree USB series
Date: Fri, 07 Mar 2014 14:30:11 +0000 [thread overview]
Message-ID: <5319D7F3.2060209@codethink.co.uk> (raw)
In-Reply-To: <1394128887-4197-1-git-send-email-ben.dooks@codethink.co.uk>
On 07/03/14 05:36, Magnus Damm wrote:
> Hi Ben,
>
> On Fri, Mar 7, 2014 at 3:01 AM, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>> This is a new series covering enabling the RCar series of SoCs USB
>> with device-tree based booting. It has been tested on the R8A7790
>> Lager board.
>>
>> Improvements from the previous series include:
>>
>> - mapping usb to the relevant phy by dt
>> - better use of existing pci of functions
>>
>> Note, there is still an issue with the second gigabyte of memory on
>> the Lager, which with current kernels causes the system to abort on
>> startup. This series will only work if the top memory area is disabled.
>
> Thanks for these patches. I think they start looking really good.
>
> In my mind there are two outstanding issues:
>
> 1) Is the USB core code change acceptable or not?
>
> The patch "[PATCH 4/9] usb: phy: check for of_node when getting phy"
> looks quite fine to me, but I wonder if the USB maintainers will
> accept it as-is or require some rework. I would say that the rest of
> this series depends on that USB core change.
I'm not sure, but without it we need to hack the PHY driver to
turn on the PHY at start time.
> 2) Per-port USB PHY driver configuration via DT
>
> Right now each USB host controller points to the same PHY device.
> Thanks for working on describing the topology! As you know, the PHY
> driver itself handles several USB ports, and I'd like to use DT to
> represent the mapping between which PHY port that maps to what USB
> Host controller to allow proper run time configuration. Right now in
> this version of the series there is no such mapping. Of course, that
> depends on proper USB PHY DT bindings...
Hmm, given the shared phy is shared and referenced counted then
I don't /think/ there is much more to be done for this. If we add
more PHYs then I would assume that each one of them would
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-03-07 14:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 18:01 Renesas RCar device-tree USB series Ben Dooks
2014-03-06 18:01 ` [PATCH 3/9] phy-rcar-usb-gen2: add device tree support Ben Dooks
2014-03-06 18:16 ` Sergei Shtylyov
2014-03-06 18:19 ` Ben Dooks
2014-03-06 19:54 ` Sergei Shtylyov
2014-03-06 18:01 ` [PATCH 5/9] ARM: shmbobile: r8a7790.dtsi: add pci0/1/2 nodes Ben Dooks
2014-03-31 22:18 ` Sergei Shtylyov
[not found] ` <1394128887-4197-1-git-send-email-ben.dooks-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2014-03-06 18:01 ` [PATCH 1/9] pci-rcar-gen2: add devicetree support Ben Dooks
2014-03-06 18:21 ` Ben Dooks
[not found] ` <5318BCAE.7000108-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2014-03-30 19:10 ` Sergei Shtylyov
2014-03-30 19:21 ` Ben Dooks
2014-03-30 19:26 ` Sergei Shtylyov
2014-03-30 19:40 ` Ben Dooks
2014-03-30 20:10 ` Sergei Shtylyov
2014-03-31 21:23 ` Sergei Shtylyov
2014-03-30 20:28 ` Sergei Shtylyov
2014-04-04 17:09 ` Bjorn Helgaas
2014-04-04 17:44 ` Ben Dooks
2014-04-04 17:46 ` Sergei Shtylyov
2014-03-06 18:01 ` [PATCH 6/9] ARM: shmobile: lager.dts: add pci 0/1/2 Ben Dooks
2014-03-06 18:01 ` [PATCH 7/9] ARM: shmobile: r8a7790.dtsi: add usbphy node Ben Dooks
2014-03-06 18:01 ` [PATCH 8/9] ARM: shmobile: lager.dts: add usbphy reference Ben Dooks
2014-03-30 19:28 ` Sergei Shtylyov
[not found] ` <5338704C.2030501-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-03-30 19:51 ` Ben Dooks
2014-03-07 5:36 ` Renesas RCar device-tree USB series Magnus Damm
2014-03-07 14:30 ` Ben Dooks [this message]
2014-03-07 16:30 ` Sergei Shtylyov
2014-03-07 16:32 ` Ben Dooks
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=5319D7F3.2060209@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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).