Hi Heiko,
On Wednesday, 21 February 2018 20:55:12 EET Heiko Stuebner wrote:
> Am Montag, 19. Februar 2018, 20:06:40 CET schrieb Laurent Pinchart:
> > On Monday, 19 February 2018 20:46:46 EET Heiko Stuebner wrote:
> > > Am Montag, 19. Februar 2018, 17:59:02 CET schrieb Laurent Pinchart:
> > > > On
Hi Laurent,
Am Montag, 19. Februar 2018, 20:06:40 CET schrieb Laurent Pinchart:
> On Monday, 19 February 2018 20:46:46 EET Heiko Stuebner wrote:
> > Am Montag, 19. Februar 2018, 17:59:02 CET schrieb Laurent Pinchart:
> > > On Friday, 16 February 2018 22:41:53 EET Heiko Stuebner wrote:
> > >> In
Hi Heiko,
On Monday, 19 February 2018 20:46:46 EET Heiko Stuebner wrote:
> Am Montag, 19. Februar 2018, 17:59:02 CET schrieb Laurent Pinchart:
> > On Friday, 16 February 2018 22:41:53 EET Heiko Stuebner wrote:
> >> In some IP implementations the reading of the phy-type may be broken.
> >> One
Hi Laurent,
Am Montag, 19. Februar 2018, 17:59:02 CET schrieb Laurent Pinchart:
> On Friday, 16 February 2018 22:41:53 EET Heiko Stuebner wrote:
> > In some IP implementations the reading of the phy-type may be broken.
> > One example are the Rockchip rk3228 and rk3328 socs that use a separate
>
Hi Heiko,
Thank you for the patch.
On Friday, 16 February 2018 22:41:53 EET Heiko Stuebner wrote:
> In some IP implementations the reading of the phy-type may be broken.
> One example are the Rockchip rk3228 and rk3328 socs that use a separate
> phy from Innosilicon but still report the
In some IP implementations the reading of the phy-type may be broken.
One example are the Rockchip rk3228 and rk3328 socs that use a separate
phy from Innosilicon but still report the HDMI20_TX type.
So allow the glue driver to force a specific type, like the vendor-phy
for these cases.
