Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755579AbdCJTRj (ORCPT ); Fri, 10 Mar 2017 14:17:39 -0500 Received: from mail-ot0-f194.google.com ([74.125.82.194]:32864 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755337AbdCJTRa (ORCPT ); Fri, 10 Mar 2017 14:17:30 -0500 MIME-Version: 1.0 In-Reply-To: <9f5d0ac4-0602-c729-5c00-1d9ef49247c1@boundarydevices.com> References: <1489121599-23206-1-git-send-email-steve_longerbeam@mentor.com> <1489121599-23206-8-git-send-email-steve_longerbeam@mentor.com> <9f5d0ac4-0602-c729-5c00-1d9ef49247c1@boundarydevices.com> From: Fabio Estevam Date: Fri, 10 Mar 2017 16:17:28 -0300 Message-ID: Subject: Re: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround To: Troy Kisky Cc: Steve Longerbeam , "robh+dt@kernel.org" , Mark Rutland , Shawn Guo , Sascha Hauer , Fabio Estevam , Russell King - ARM Linux , mchehab@kernel.org, Hans Verkuil , Nick Dyer , markus.heiser@darmarit.de, Philipp Zabel , Laurent Pinchart , bparrot@ti.com, Geert Uytterhoeven , Arnd Bergmann , Sudip Mukherjee , minghsiu.tsai@mediatek.com, Tiffany Lin , Jean-Christophe TROTIN , horms+renesas@verge.net.au, niklas.soderlund+renesas@ragnatech.se, Robert Jarzmik , songjun.wu@microchip.com, andrew-ct.chen@mediatek.com, Greg Kroah-Hartman , shuah@kernel.org, sakari.ailus@linux.intel.com, Pavel Machek , devel@driverdev.osuosl.org, "devicetree@vger.kernel.org" , Steve Longerbeam , linux-kernel , "linux-arm-kernel@lists.infradead.org" , linux-media Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1554 Lines: 39 On Fri, Mar 10, 2017 at 3:59 PM, Troy Kisky 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 >> --- >> 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.