From: Gary Bisson <bisson.gary@gmail.com>
To: Eric Nelson <eric.nelson@boundarydevices.com>,
meta-freescale@yoctoproject.org
Cc: fabio.estevam@freescale.com
Subject: Re: Patch submission to Freescale kernel
Date: Tue, 02 Dec 2014 10:24:29 -0800 [thread overview]
Message-ID: <547E03DD.9060204@gmail.com> (raw)
In-Reply-To: <547DD52A.8090504@boundarydevices.com>
Eric, All,
On 12/02/2014 07:05 AM, Eric Nelson wrote:
> Hi Gary,
>
> On 12/01/2014 09:18 PM, Gary Bisson wrote:
>> Hi,
>>
>> I was wondering what was the procedure to submit a patch to the
>> Freescale maintained kernel:
>> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/
>>
>> I've just made a patch that fixes the display issue for rev T1.0 of the
>> SoC which has been previously reported:
>> https://lists.yoctoproject.org/pipermail/meta-freescale/2014-May/008553.html
>>
>> "mxc_sdc_fb fb.27: timeout when waiting for flip irq"
>>
>> Then, I'd like to send that patch over to the fslc and mainline kernels
>> as they seem to have the issue by checking their source code.
>>
> Cool! That discussion on i.MX Community ended with the realization
> that the issue was specific to TO 1.0 silicon.
>
> Are you running on that silicon version? (this is shown in the first
> few lines of U-Boot output)
Yes I confirm I am running on this revision and the (ridiculously small)
patch happens in those IMX_CHIP_REVISION test cases.
>> Regarding the mainline kernel, I can't seem to get the HDMI (on
>> nitrogen6x) to work at all no matter which revision/board I use. Looking
>> into the source code I've seen the evolution of the
>> drivers/staging/imx-drm driver which tends to say that HDMI is
>> supported. If so, would anyone have some insights on which command line
>> to pass the kernel in order to get the mainline kernel to recognize the
>> HDMI display properly. So far the init seems to be fine but fb0 sysfs
>> modes is just rubbish.
>> [ 1.863506] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops
>> ipu_crtc_ops)
>> [ 1.863719] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops
>> ipu_crtc_ops)
>> [ 1.863955] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops
>> ipu_crtc_ops)
>> [ 1.864168] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops
>> ipu_crtc_ops)
>> [ 1.867758] imx-hdmi 120000.hdmi: Detected HDMI controller
>> 0x13:0xa:0xa0:0xc1
>> [ 1.868066] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
>> [ 1.868537] imx-drm display-subsystem: bound
>> 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)
>>
> Hmmm. This worked for me the last time I checked (using Shawn's tree).
>
> I'll double check and report back.
Great thanks! I suspect my command line to be wrong though as I think
mxcfb0 video parameters do not apply on mainline.
But I'll try out Fabio's suggestion of removing the LVDS node.
Thanks,
Gary
next prev parent reply other threads:[~2014-12-02 18:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 4:18 Patch submission to Freescale kernel Gary Bisson
2014-12-02 10:42 ` Otavio Salvador
2014-12-02 18:23 ` Gary Bisson
2014-12-02 11:16 ` Fabio Estevam
2014-12-02 15:05 ` Eric Nelson
2014-12-02 18:24 ` Gary Bisson [this message]
2014-12-02 19:09 ` [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support Eric Nelson
2014-12-02 19:11 ` Eric Nelson
2014-12-02 19:14 ` Gary Bisson
2014-12-02 19:17 ` Fabio Estevam
2014-12-02 19:52 ` Gary Bisson
2014-12-02 20:11 ` Eric Nelson
2014-12-02 20:16 ` Gary Bisson
2014-12-02 21:04 ` Eric Nelson
2014-12-02 22:11 ` Eric Nelson
2014-12-02 21:15 ` Fabio Estevam
2014-12-02 20:06 ` Eric Nelson
2014-12-02 21:16 ` Fabio Estevam
2014-12-02 21:20 ` Eric Nelson
2014-12-02 21:37 ` Gary Bisson
2014-12-02 22:44 ` Eric Nelson
2014-12-02 22:54 ` Gary Bisson
2014-12-02 23:11 ` Eric Nelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547E03DD.9060204@gmail.com \
--to=bisson.gary@gmail.com \
--cc=eric.nelson@boundarydevices.com \
--cc=fabio.estevam@freescale.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.