From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: i.MX27: Configure GPIOs as "input" by default
Date: Wed, 4 Dec 2013 12:58:53 +0100 [thread overview]
Message-ID: <20131204125853.57b79cda@ipc1.ka-ro> (raw)
In-Reply-To: <1386156787.576977781@f410.i.mail.ru>
Hi,
Alexander Shiyan wrote:
> > > > > > > > > > On Sat, Nov 30, 2013 at 11:03:20AM +0400, Alexander Shiyan wrote:
> > > > > > > > > > > This patch changes the default direction for pins used
> > > > > > > > > > > as GPIO to "input". This prevents a short circuit on the
> > > > > > > > > > > configuration stage when GPIO-pin is connected to the
> > > > > > > > > > > other output pin.
> > > > > > > > > >
> > > > > > > > > > Markus,
> > > > > > > > > >
> > > > > > > > > > Does it make sense to you?
> > > > > > > > >
> > > > > > > > > I am not sure if this really happens. However, it does make sense and I
> > > > > > > > > can't see any disadvantages in changing the default GPIO mux direction to
> > > > > > > > > input.
> > > > > > > > >
> > > > > > > > What happens, if the bootloader already set up a pin as output and
> > > > > > > > linux later does the pinconfig stuff?
> > > > > > > > If the pin is reconfigured as input then, this may produce an unwanted
> > > > > > > > glitch on the pin. IMO the pinconfig driver should not touch the pin
> > > > > > > > direction, but leave it to the gpio driver to set that up.
> > > > > > >
> > > > > > > Such pin can be overridden by board DTS.
> > > > > > >
> > > > > > So, which pins will be configured with the default direction?
> > > > > > If pins are not stated in DT they should be not configured at all, I
> > > > > > suppose.
> > > > >
> > > > > Yes. We talk about GPIOs defined in DTS.
> > > > > Just one example: We have one GPIO pin connected to switch between ground
> > > > > and resistor to pullup (gpio-key driver). When pinctrl driver will initialize pin for the
> > > > > driver (before gpio_direction_input() in the driver), direction will be set to output
> > > > > and this may cause short circuit.
> > > > >
> > > > The pin direction should be determined by the GPIO driver, not the
> > >
> > > Direction determined by driver that use this GPIO pin,
> > > setup this direction should be by GPIO driver.
> > >
> > > > pinctrl driver. Pins that have been set up correctly by the bootloader
> > > > must not change their direction when the pinctrl driver reconfigures
> > > > the pins!
> > >
> > > Yes. But this is another topic for discussion, it does not concern with this patch.
> > >
> > If the pin direction is not being determined by the pinctrl driver the
> > patch to change the default direction would not be necessary.
> >
> > Otherwise this patch would try to exorcise the devil with the help of
> > beelzebub.
> >
> > A short between to outputs is to be prevented as well as a temporary
> > reconfiguration of an output pin to input.
>
> Current "pinctrl-imx1-core.c" touch direction register for any pin.
> As far this not fixed, this will be a temporary solution.
>
Then that driver should be fixed instead of fixing one bug by
implementing another one.
Lothar Wa?mann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________
next prev parent reply other threads:[~2013-12-04 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 7:03 [PATCH] ARM: dts: i.MX27: Configure GPIOs as "input" by default Alexander Shiyan
2013-12-03 8:46 ` Shawn Guo
2013-12-03 13:30 ` Markus Pargmann
2013-12-04 8:57 ` Lothar Waßmann
2013-12-04 9:04 ` Alexander Shiyan
2013-12-04 9:13 ` Lothar Waßmann
2013-12-04 9:24 ` Alexander Shiyan
2013-12-04 10:07 ` Lothar Waßmann
2013-12-04 10:16 ` Alexander Shiyan
2013-12-04 11:15 ` Lothar Waßmann
2013-12-04 11:33 ` Alexander Shiyan
2013-12-04 11:58 ` Lothar Waßmann [this message]
2013-12-03 13:37 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131204125853.57b79cda@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.