From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934240AbdCJWFN (ORCPT ); Fri, 10 Mar 2017 17:05:13 -0500 Received: from mail-oi0-f67.google.com ([209.85.218.67]:36290 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932482AbdCJWFE (ORCPT ); Fri, 10 Mar 2017 17:05:04 -0500 MIME-Version: 1.0 In-Reply-To: <20170310215731.GB6540@amd> 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> <20170310215731.GB6540@amd> From: Fabio Estevam Date: Fri, 10 Mar 2017 19:05:02 -0300 Message-ID: Subject: Re: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround To: Pavel Machek Cc: Troy Kisky , 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, 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 On Fri, Mar 10, 2017 at 6:57 PM, Pavel Machek wrote: > And it should not depend on configuration. Hardware vendor should be > able to ship board with working device tree... We are talking about pin conflict here. Please read the commit log of this patch for details. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Estevam Subject: Re: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround Date: Fri, 10 Mar 2017 19:05:02 -0300 Message-ID: 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> <20170310215731.GB6540@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20170310215731.GB6540@amd> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Pavel Machek Cc: Troy Kisky , Steve Longerbeam , "robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , Mark Rutland , Shawn Guo , Sascha Hauer , Fabio Estevam , Russell King - ARM Linux , mchehab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Hans Verkuil , Nick Dyer , markus.heiser-m1Uo1GnMJf0b1SvskN2V4Q@public.gmane.org, Philipp Zabel , Laurent Pinchart , bparrot-l0cyMroinI0@public.gmane.org, Geert Uytterhoeven , Arnd Bergmann , Sudip Mukherjee , minghsiu.tsai-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org, Tiffany Lin , Jean-Christophe List-Id: devicetree@vger.kernel.org On Fri, Mar 10, 2017 at 6:57 PM, Pavel Machek wrote: > And it should not depend on configuration. Hardware vendor should be > able to ship board with working device tree... We are talking about pin conflict here. Please read the commit log of this patch for details. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-oi0-f67.google.com ([209.85.218.67]:36290 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932482AbdCJWFE (ORCPT ); Fri, 10 Mar 2017 17:05:04 -0500 MIME-Version: 1.0 In-Reply-To: <20170310215731.GB6540@amd> 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> <20170310215731.GB6540@amd> From: Fabio Estevam Date: Fri, 10 Mar 2017 19:05:02 -0300 Message-ID: Subject: Re: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround To: Pavel Machek Cc: Troy Kisky , 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, 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-media-owner@vger.kernel.org List-ID: On Fri, Mar 10, 2017 at 6:57 PM, Pavel Machek wrote: > And it should not depend on configuration. Hardware vendor should be > able to ship board with working device tree... We are talking about pin conflict here. Please read the commit log of this patch for details. From mboxrd@z Thu Jan 1 00:00:00 1970 From: festevam@gmail.com (Fabio Estevam) Date: Fri, 10 Mar 2017 19:05:02 -0300 Subject: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround In-Reply-To: <20170310215731.GB6540@amd> 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> <20170310215731.GB6540@amd> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Mar 10, 2017 at 6:57 PM, Pavel Machek wrote: > And it should not depend on configuration. Hardware vendor should be > able to ship board with working device tree... We are talking about pin conflict here. Please read the commit log of this patch for details.