On Tue, Aug 30, 2022 at 10:35:24AM +0530, Vinod Koul wrote:
> On 18-07-22, 14:17, Johan Hovold wrote:
> > On Thu, Jul 14, 2022 at 02:43:03PM +0200, Johan Hovold wrote:
> > > When adding support for SC8280XP to the QMP PHY driver I noticed that
> > > the PHY provider child node was not described by the current DT schema.
> > >
> > > The SC8280XP PHYs also need a second fixed-divider PIPE clock
> > > ("pipediv2") and I didn't want to have to add a bogus "lane" suffix to
> > > the clock name just to match the current "pipe0" name so I decided to
> > > deprecate the unnecessary suffix in the current binding instead.
> > >
> > > To be able to add the missing child-node schema and handle device
> > > specifics like additional PIPE clocks, it quickly became obvious that
> > > the binding needs to be split up.
> > >
> > > This series clean up and fixes some issue with the current schema before
> > > splitting it up in separate schemas for PCIe, UFS and USB and adding
> > > missing parts like the child PHY provider nodes.
> > >
> > > The MSM8996 PCIe PHY gets its own schema as this is the only non-combo
> > > PHY that actually provides more than one PHY per IP block. Note that the
> > > "lane" suffix is still unnecessary and misleading.
> > >
> > > The final patches add support for the updated binding to the (recently
> > > split up) PHY drivers. Included is also a related combo PHY cleanup.
> >
> > Hi Vinod,
> >
> > any chance of getting these into 5.20?
> >
> > Note that there'll be an -rc8 on Sunday.
>
> Sorry phy tree goes thru char-misc and it was already sent and closed,
> so couldnt do the needful
Yeah, it was a bit of a wild shot, but I noticed you hadn't actually
sent your PR to Greg yet when I pinged you.
Johan
