From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757308AbcAJTCU (ORCPT ); Sun, 10 Jan 2016 14:02:20 -0500 Received: from metis.ext.4.pengutronix.de ([92.198.50.35]:54715 "EHLO metis.ext.4.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756993AbcAJTCT (ORCPT ); Sun, 10 Jan 2016 14:02:19 -0500 Date: Sun, 10 Jan 2016 20:01:58 +0100 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Stefan Wahren Cc: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= , Mark Rutland , devicetree@vger.kernel.org, Russell King , Pawel Moll , Ian Campbell , linux-kernel@vger.kernel.org, Rob Herring , Sascha Hauer , Kumar Gala , Shawn Guo , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: dts: imx28: add pinmux for USB1 overcurrent on pwm2 Message-ID: <20160110190158.GK24441@pengutronix.de> References: <1452429613-28783-1-git-send-email-mans@mansr.com> <1473600647.505612.cb24b396-67be-4b7b-9938-7cb30ef4fe05.open-xchange@email.1und1.de> <89586980.506110.cb24b396-67be-4b7b-9938-7cb30ef4fe05.open-xchange@email.1und1.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <89586980.506110.cb24b396-67be-4b7b-9938-7cb30ef4fe05.open-xchange@email.1und1.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Sun, Jan 10, 2016 at 02:38:00PM +0100, Stefan Wahren wrote: > > Måns Rullgård hat am 10. Januar 2016 um 14:13 geschrieben: > > Stefan Wahren writes: > > > > > Hi Mans, > > > > > >> Mans Rullgard hat am 10. Januar 2016 um 13:40 geschrieben: > > >> > > >> > > >> Add pinmux setting for USB1 overcurrent on pwm2 pad. > > > > > > could you please change your patch to describe why you need to add > > > this pinmux? > > > > I'm working on a board that is wired that way. I can of course put this > > in the board-specific dts if that's preferable. > > So the board isn't submitted to mainline? > > IMHO the change is okay, but the description doesn't explain why is it needed. > > So a suitable description would be that it's needed for board xy. The problem with pinmuxing on i.MX23/28 is that the order of pinmux groups is to a certain degree important. So not everything is possible in the machine specific dts. (I didn't have an eye on this issue, maybe it's fixed in the meantime?) Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ |