From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 47D75E00521; Tue, 2 Dec 2014 10:24:34 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (bisson.gary[at]gmail.com) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.192.171 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 48409E002F9 for ; Tue, 2 Dec 2014 10:24:31 -0800 (PST) Received: by mail-pd0-f171.google.com with SMTP id y13so13702191pdi.30 for ; Tue, 02 Dec 2014 10:24:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5dLLgvD7QNVrk4B5yPbrM/2gvNjrgL5khJdy26ul0hk=; b=J0ah39+yyzqEt/ZgIURZAxxkPLqZBgMDHgy5DsrhQw3e9XCcrbZ1S8tEAkW0cD7A/e 1hRgJvmgp3OWycqQ0yq8XqBb+1Wpk/gNsKnQkQJkgbzzof5mTfotntePIiwBOrvvsZYU NrOowf+ZrKg0l+Q6V7ZFMXNeKsnNmahNx6YyoQ4Mg/8FGP00r5Uw2dvzSgWpGcussOCt U1Ut3n0LN5jmfOIm7VT28HPgZb0cxfk2k/bdLDepgt7BxoUUptpecQDm1WgFEDJvcWez 4e1afnZ4Z/IHM6ta+yv+tnUtx7qDf9IPbpFylaA156nGr+3D8gmvrG1r4CHwyrwNFne7 lMXQ== X-Received: by 10.68.136.6 with SMTP id pw6mr7947556pbb.157.1417544671399; Tue, 02 Dec 2014 10:24:31 -0800 (PST) Received: from [172.16.20.247] (173-10-76-58-BusName-Washington.hfc.comcastbusiness.net. [173.10.76.58]) by mx.google.com with ESMTPSA id of9sm20897405pbc.6.2014.12.02.10.24.30 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Dec 2014 10:24:30 -0800 (PST) Message-ID: <547E03DD.9060204@gmail.com> Date: Tue, 02 Dec 2014 10:24:29 -0800 From: Gary Bisson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 MIME-Version: 1.0 To: Eric Nelson , meta-freescale@yoctoproject.org References: <547D3D8C.5010707@gmail.com> <547DD52A.8090504@boundarydevices.com> In-Reply-To: <547DD52A.8090504@boundarydevices.com> Cc: fabio.estevam@freescale.com Subject: Re: Patch submission to Freescale kernel X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 18:24:34 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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