From mboxrd@z Thu Jan 1 00:00:00 1970 From: shawn.guo@linaro.org (Shawn Guo) Date: Mon, 17 Feb 2014 10:19:53 +0800 Subject: [PATCH 1/2] ARM: dts: imx6qdl-sabresd: Add hog entry for GPIO4_10 In-Reply-To: References: <1392306839-10736-1-git-send-email-fabio.estevam@freescale.com> <20140217020519.GC9879@S2101-09.ap.freescale.net> Message-ID: <20140217021951.GE9879@S2101-09.ap.freescale.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, Feb 16, 2014 at 11:11:40PM -0300, Fabio Estevam wrote: > On Sun, Feb 16, 2014 at 11:05 PM, Shawn Guo wrote: > > On Thu, Feb 13, 2014 at 01:53:58PM -0200, Fabio Estevam wrote: > >> GPIO4_10 is the GPIO used to turn on the regulator that powers up the codec. > >> > >> Add a hog entry for it. > > > > I'm going to be strict on hog pin use. It does not sound like a true > > hog pin. Is it possible to have a pinctrl state for that regulator > > setting this pin up? > > Could you please explain when a pin should or should not be placed > into the hog group? The hog group is for those pins that do not belong to any particular client device. IOW, we should only put a pin into hog group when it can not be put into any client device's pinctrl state. Shawn