On Mon, Jun 16, 2014 at 11:13:02AM -0300, Fabio Estevam wrote:
> On Wed, Jun 11, 2014 at 5:17 AM, Russell King - ARM Linux
> wrote:
>
> > The problem here is that we need more inteligence from CCF in order to
> > do that - we need it to be able to reprogram the dividers so that the
> > IPU DI0 cl
On Wed, Jun 11, 2014 at 5:17 AM, Russell King - ARM Linux
wrote:
> The problem here is that we need more inteligence from CCF in order to
> do that - we need it to be able to reprogram the dividers so that the
> IPU DI0 clock remains at 148.5MHz while increasing the output of
> pll5_video_div thr
Hi Russell,
Am Mittwoch, den 11.06.2014, 09:17 +0100 schrieb Russell King - ARM
Linux:
> On Tue, Jun 10, 2014 at 10:32:25AM -0300, Fabio Estevam wrote:
> > On Tue, Jun 10, 2014 at 9:58 AM, Fabio Estevam
> > wrote:
> > > On Mon, Jun 9, 2014 at 5:09 PM, Russell King - ARM Linux
> > > wrote:
> > >
On Tue, Jun 10, 2014 at 10:32:25AM -0300, Fabio Estevam wrote:
> On Tue, Jun 10, 2014 at 9:58 AM, Fabio Estevam wrote:
> > On Mon, Jun 9, 2014 at 5:09 PM, Russell King - ARM Linux
> > wrote:
> >
> >> Right, so the problem isn't at the HDMI level, but at the DI level... so
> >> that's where we nee
On Tue, Jun 10, 2014 at 05:14:21PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 10, 2014 at 04:13:06PM +0100, Russell King - ARM Linux wrote:
> > where 'M' is the IPU DI clock muxer. However, we're currently setting
> > this up as:
> >
> > LM --+ LDB serial
> > `- /7
On Tue, Jun 10, 2014 at 04:13:06PM +0100, Russell King - ARM Linux wrote:
> where 'M' is the IPU DI clock muxer. However, we're currently setting
> this up as:
>
> LM --+ LDB serial
> `- /7 -+ LDB DI clock
> IPM --- /N IM --- IPU DI clock
>
> and hoping that th
On Tue, Jun 10, 2014 at 09:58:54AM -0300, Fabio Estevam wrote:
> Booting the kernel with the HDMI cable connected (no image is seen on
> HDMI, only on LVDS):
Reformatting a bit:
> disp 0: panel size = 1920 x 1080
> Clocks: IPU 26400Hz DI 2400Hz Needed 13850Hz
> IPU clock can give 13
Hi Tim,
On Tue, Jun 10, 2014 at 3:54 PM, Tim Harvey wrote:
> Fabio,
>
> I'm following along with this thread as I see the same thing you do on
> our Ventana boards that support both LVDS and HDMI: without
> hot-plugging the HDMI connector I get not HDMI out simply by having
> the LVDS node popul
On Tue, Jun 10, 2014 at 2:04 PM, Russell King - ARM Linux
wrote:
> This diagram is drawn from the code in clk-imx6.c, and it does not
> agree with what is in the SoC manuals - this is the representation
> redrawn from the manuals:
> The difference is, there is no clock gate between the LDB
On Mon, Jun 9, 2014 at 7:29 AM, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
> wrote:
>
>> Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
>> should report the current state of the hotplug detection.
>
> /sys/class/drm/card0-HDMI-A-1/stat
On Tue, Jun 10, 2014 at 9:58 AM, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 5:09 PM, Russell King - ARM Linux
> wrote:
>
>> Right, so the problem isn't at the HDMI level, but at the DI level... so
>> that's where we need to debug what's being setup. I left some debugging
>> in ipu-di.c - coul
On Mon, Jun 9, 2014 at 5:09 PM, Russell King - ARM Linux
wrote:
> Right, so the problem isn't at the HDMI level, but at the DI level... so
> that's where we need to debug what's being setup. I left some debugging
> in ipu-di.c - could you try enabling that please?
Booting the kernel with the HD
On Mon, Jun 09, 2014 at 11:29:28AM -0300, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
> wrote:
>
> > Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
> > should report the current state of the hotplug detection.
>
> /sys/class/drm/card0-
On Mon, Jun 09, 2014 at 03:47:46PM -0300, Fabio Estevam wrote:
> Also tested keeping LVDS parent as PLL5 and reverted this commit:
>
> commit 17b9b3b9e88ac6564689283a08034faf2c048fdb
> Author: Sascha Hauer
> Date: Mon Apr 14 16:20:39 2014 +0200
>
> ARM: imx6q: clk: Parent DI clocks to vide
On Mon, Jun 09, 2014 at 03:38:55PM -0300, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 3:15 PM, Fabio Estevam wrote:
> >> I wonder if the problem is that HDMI and LVDS are interfering with each
> >> other wrt the required pixel clock, and LVDS is winning. If we have
> >> HDMI enabled, many HDMI
On Mon, Jun 09, 2014 at 03:15:16PM -0300, Fabio Estevam wrote:
> With HDMI cable connected (no image is seen on HDMI, only on lvds cable):
>
> imx-drm display-subsystem.11: bound 12.hdmi (ops hdmi_ops)
> imx-hdmi 12.hdmi: EVENT=plugin
> imx-hdmi 12.hdmi: Non-CEA mode used in HDMI
> imx
On Mon, Jun 09, 2014 at 11:29:28AM -0300, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
> wrote:
>
> > Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
> > should report the current state of the hotplug detection.
>
> /sys/class/drm/card0-
On Mon, Jun 9, 2014 at 5:09 PM, Russell King - ARM Linux
wrote:
> Right, so the problem isn't at the HDMI level, but at the DI level... so
> that's where we need to debug what's being setup. I left some debugging
> in ipu-di.c - could you try enabling that please?
Sure, will capture the logs to
On Mon, Jun 9, 2014 at 3:38 PM, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 3:15 PM, Fabio Estevam wrote:
>>> I wonder if the problem is that HDMI and LVDS are interfering with each
>>> other wrt the required pixel clock, and LVDS is winning. If we have
>>> HDMI enabled, many HDMI sinks will o
On Mon, Jun 9, 2014 at 3:15 PM, Fabio Estevam wrote:
>> I wonder if the problem is that HDMI and LVDS are interfering with each
>> other wrt the required pixel clock, and LVDS is winning. If we have
>> HDMI enabled, many HDMI sinks will only work if we set one of their
>> supported modes (with th
On Mon, Jun 9, 2014 at 2:49 PM, Russell King - ARM Linux
wrote:
> On Mon, Jun 09, 2014 at 11:29:28AM -0300, Fabio Estevam wrote:
>> On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
>> wrote:
>>
>> > Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
>> > should report
On Mon, Jun 09, 2014 at 10:44:14AM -0300, Fabio Estevam wrote:
> Russell,
>
> On Fri, Jun 6, 2014 at 10:56 AM, Russell King
> wrote:
> > The initial state at boot is assumed to be disconnected, and we hope
> > to receive an interrupt to update the status. Let's be more explicit
> > about the cur
On Mon, Jun 9, 2014 at 11:33 AM, Shawn Guo wrote:
> On Mon, Jun 09, 2014 at 11:29:28AM -0300, Fabio Estevam wrote:
>> On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
>> wrote:
>>
>> > Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
>> > should report the current s
On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
wrote:
> Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
> should report the current state of the hotplug detection.
/sys/class/drm/card0-HDMI-A-1/status returns the correct state for
HDMI cable connection.
> Remem
Russell,
On Fri, Jun 6, 2014 at 10:56 AM, Russell King
wrote:
> The initial state at boot is assumed to be disconnected, and we hope
> to receive an interrupt to update the status. Let's be more explicit
> about the current state - reading the PHY status register tells us
> the current level of
The initial state at boot is assumed to be disconnected, and we hope
to receive an interrupt to update the status. Let's be more explicit
about the current state - reading the PHY status register tells us
the current level of the hotplug signal, which we can report back in
the _detect() method.
S
On Fri, Jun 06, 2014 at 02:56:43PM +0100, Russell King wrote:
> The initial state at boot is assumed to be disconnected, and we hope
> to receive an interrupt to update the status. Let's be more explicit
> about the current state - reading the PHY status register tells us
> the current level of th
27 matches
Mail list logo
