Hi Jose,
On Tuesday 13 Jun 2017 15:11:27 Jose Abreu wrote:
> Hi Laurent,
>
> Sorry for the late reply!
No worries.
> On 10-06-2017 09:50, Laurent Pinchart wrote:
> > On Friday 09 Jun 2017 13:53:12 Jose Abreu wrote:
> >> On 09-06-2017 12:04, Jose Abreu wrote:
> >>> Currently HDMI 2.0 PHYs do
Hi Jose,
On Tuesday 13 Jun 2017 15:11:27 Jose Abreu wrote:
> Hi Laurent,
>
> Sorry for the late reply!
No worries.
> On 10-06-2017 09:50, Laurent Pinchart wrote:
> > On Friday 09 Jun 2017 13:53:12 Jose Abreu wrote:
> >> On 09-06-2017 12:04, Jose Abreu wrote:
> >>> Currently HDMI 2.0 PHYs do
Hi, Jose:
The value of RK3399 reg HDMI_CONFIG2_ID is 0xf3.
Using hdmi_phy_configure_dwc_hdmi_3d_tx() for hdmi 2.0 phy, we test
all HDMI video mode(including 594MHz) and it woks good.
And our customer has pass the HDMI CTS.
If you send a patch with a general config function
Hi, Jose:
The value of RK3399 reg HDMI_CONFIG2_ID is 0xf3.
Using hdmi_phy_configure_dwc_hdmi_3d_tx() for hdmi 2.0 phy, we test
all HDMI video mode(including 594MHz) and it woks good.
And our customer has pass the HDMI CTS.
If you send a patch with a general config function
Hi Jose
Sorry miss your email and Sorry for the late reply
I can sure that your patch works on our rk3399 platform.
my internal kernel already has similar patch, using
hdmi_phy_configure_dwc_hdmi_3d_tx() for hdmi 2.0 phy,
good works with many video modes (4k, 1080p, 720p etc.), I'm not
Hi Jose
Sorry miss your email and Sorry for the late reply
I can sure that your patch works on our rk3399 platform.
my internal kernel already has similar patch, using
hdmi_phy_configure_dwc_hdmi_3d_tx() for hdmi 2.0 phy,
good works with many video modes (4k, 1080p, 720p etc.), I'm not
Hi Jose,
Am Freitag, 9. Juni 2017, 13:53:12 CEST schrieb Jose Abreu:
> On 09-06-2017 12:04, Jose Abreu wrote:
> > Currently HDMI 2.0 PHYs do not have a default configuration function.
> >
> > As these PHYs have the same register layout as the 3D PHYs we can
> > safely use the default
Hi Jose,
Am Freitag, 9. Juni 2017, 13:53:12 CEST schrieb Jose Abreu:
> On 09-06-2017 12:04, Jose Abreu wrote:
> > Currently HDMI 2.0 PHYs do not have a default configuration function.
> >
> > As these PHYs have the same register layout as the 3D PHYs we can
> > safely use the default
Hi Laurent,
Sorry for the late reply!
On 10-06-2017 09:50, Laurent Pinchart wrote:
> Hi Jose,
>
> On Friday 09 Jun 2017 13:53:12 Jose Abreu wrote:
>> On 09-06-2017 12:04, Jose Abreu wrote:
>>> Currently HDMI 2.0 PHYs do not have a default configuration function.
>>>
>>> As these PHYs have the
Hi Laurent,
Sorry for the late reply!
On 10-06-2017 09:50, Laurent Pinchart wrote:
> Hi Jose,
>
> On Friday 09 Jun 2017 13:53:12 Jose Abreu wrote:
>> On 09-06-2017 12:04, Jose Abreu wrote:
>>> Currently HDMI 2.0 PHYs do not have a default configuration function.
>>>
>>> As these PHYs have the
Hi Jose,
On Friday 09 Jun 2017 13:53:12 Jose Abreu wrote:
> On 09-06-2017 12:04, Jose Abreu wrote:
> > Currently HDMI 2.0 PHYs do not have a default configuration function.
> >
> > As these PHYs have the same register layout as the 3D PHYs we can
> > safely use the default configuration
Hi Jose,
On Friday 09 Jun 2017 13:53:12 Jose Abreu wrote:
> On 09-06-2017 12:04, Jose Abreu wrote:
> > Currently HDMI 2.0 PHYs do not have a default configuration function.
> >
> > As these PHYs have the same register layout as the 3D PHYs we can
> > safely use the default configuration
Hi Mark,
On 09-06-2017 12:04, Jose Abreu wrote:
> Currently HDMI 2.0 PHYs do not have a default configuration function.
>
> As these PHYs have the same register layout as the 3D PHYs we can
> safely use the default configuration function.
I may have been a little to fast arriving at this
Hi Mark,
On 09-06-2017 12:04, Jose Abreu wrote:
> Currently HDMI 2.0 PHYs do not have a default configuration function.
>
> As these PHYs have the same register layout as the 3D PHYs we can
> safely use the default configuration function.
I may have been a little to fast arriving at this
14 matches
Mail list logo