[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5BNrSEyrbWbCBCbsy4yTrh4AHfk2Too0qHuffxqUCgADg@mail.gmail.com>
Date: Fri, 10 Mar 2017 16:17:28 -0300
From: Fabio Estevam <festevam@...il.com>
To: Troy Kisky <troy.kisky@...ndarydevices.com>
Cc: Steve Longerbeam <slongerbeam@...il.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
mchehab@...nel.org, Hans Verkuil <hverkuil@...all.nl>,
Nick Dyer <nick@...anahar.org>, markus.heiser@...marit.de,
Philipp Zabel <p.zabel@...gutronix.de>,
Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
bparrot@...com, Geert Uytterhoeven <geert@...ux-m68k.org>,
Arnd Bergmann <arnd@...db.de>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
minghsiu.tsai@...iatek.com, Tiffany Lin <tiffany.lin@...iatek.com>,
Jean-Christophe TROTIN <jean-christophe.trotin@...com>,
horms+renesas@...ge.net.au, niklas.soderlund+renesas@...natech.se,
Robert Jarzmik <robert.jarzmik@...e.fr>,
songjun.wu@...rochip.com, andrew-ct.chen@...iatek.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
shuah@...nel.org, sakari.ailus@...ux.intel.com,
Pavel Machek <pavel@....cz>, devel@...verdev.osuosl.org,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Steve Longerbeam <steve_longerbeam@...tor.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-media <linux-media@...r.kernel.org>
Subject: Re: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum
ERR006687 workaround
On Fri, Mar 10, 2017 at 3:59 PM, Troy Kisky
<troy.kisky@...ndarydevices.com> wrote:
> On 3/9/2017 8:52 PM, Steve Longerbeam wrote:
>> There is a pin conflict with GPIO_6. This pin functions as a power
>> input pin to the OV5642 camera sensor, but ENET uses it as the h/w
>> workaround for erratum ERR006687, to wake-up the ARM cores on normal
>> RX and TX packet done events. So we need to remove the h/w workaround
>> to support the OV5642. The result is that the CPUidle driver will no
>> longer allow entering the deep idle states on the sabrelite.
>>
>> This is a partial revert of
>>
>> commit 6261c4c8f13e ("ARM: dts: imx6qdl-sabrelite: use GPIO_6 for FEC
>> interrupt.")
>> commit a28eeb43ee57 ("ARM: dts: imx6: tag boards that have the HW workaround
>> for ERR006687")
>>
>> Signed-off-by: Steve Longerbeam <steve_longerbeam@...tor.com>
>> ---
>> arch/arm/boot/dts/imx6qdl-sabrelite.dtsi | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi b/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
>> index 8413179..89dce27 100644
>> --- a/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
>> +++ b/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
>> @@ -270,9 +270,6 @@
>> txd1-skew-ps = <0>;
>> txd2-skew-ps = <0>;
>> txd3-skew-ps = <0>;
>
> How about
>
> +#if !IS_ENABLED(CONFIG_VIDEO_OV5642)
Or maybe just create a new device tree for using the camera, like
imx6q-sabrelite-camera.dts.
This way we can keep the FEC erratum for the existing sabrelite dtb's.
Powered by blists - more mailing lists