lkml.org 
[lkml]   [2014]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v3 0/5] phy: miphy365x: Introduce support for MiPHY365x
Hi,

On Monday 21 July 2014 01:09 PM, Lee Jones wrote:
> Hi Kishon,
>
>>> This patchset is based on the two core patches you sent to the
>>> list which facilitate creating PHYs residing on multi-channel
>>> controllers. The changes since the last submission centre
>>> around dynamic PHY creation based solely on what is provided via
>>> Device Tree, as requested. The other review comments have also
>>> been addressed in this set.
>>
>> Merged the first four patches of this series. (merged v3+1 for 1st patch).
>> I'm not sure who would be merging the dt patch (5/5). But for now I've merged
>> 2/5 in linux-phy tree since the phy patch seems to be dependent on it.
>> So the dt patch can be merged only after -rc1. However if whoever merges
>> dt wants to get it merged during the merge window, I can prepare a common
>> branch which both of us can merge to. Either ways, dt Maintainer should
>> let me know.
>
> Thanks for applying. It would be really helpful if you could put just
> patch 2/5 onto an immutable branch and provide a tag e that Maxime
> could pull from.

Sure. Created tag
git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git
miphy365x_dt_common_header (branch:miphy365x_dt_header). It is based on 3.16-rc5.

Thanks
Kishon
>
> Kind regards,
> Lee
>
>>> .../devicetree/bindings/phy/phy-miphy365x.txt | 76 +++
>>> arch/arm/boot/dts/stih416-b2020-revE.dts | 10 +
>>> arch/arm/boot/dts/stih416-b2020.dts | 12 +
>>> arch/arm/boot/dts/stih416.dtsi | 22 +
>>> drivers/phy/Kconfig | 10 +
>>> drivers/phy/Makefile | 1 +
>>> drivers/phy/phy-miphy365x.c | 636 +++++++++++++++++++++
>>> include/dt-bindings/phy/phy-miphy365x.h | 14 +
>>> 8 files changed, 781 insertions(+)
>


\
 
 \ /
  Last update: 2014-07-22 10:41    [W:0.169 / U:0.596 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site