From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Marc Gonzalez <marc.w.gonzalez@free.fr>,
Marc Zyngier <marc.zyngier@arm.com>,
MSM <linux-arm-msm@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
GPIO <linux-gpio@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Using a GPIO as an interrupt line
Date: Tue, 19 Nov 2019 11:00:31 +0000 [thread overview]
Message-ID: <20191119110030.GA25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191119105619.4osmin7m5ryqfwih@pengutronix.de>
On Tue, Nov 19, 2019 at 11:56:19AM +0100, Uwe Kleine-König wrote:
> Having a pin configured as GPIO is the boot default setting for many
> SoCs/pins. So you might get away with not specifying a setting for pin
> 42, but that's not as robust as configuring that explicitly.
If only that was universally true - the LX2160A as an example doesn't
default to GPIO mode... just be very aware of what the documentation,
and, as the saying goes "if there is any doubt, there is no doubt".
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-11-19 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 9:28 Using a GPIO as an interrupt line Marc Gonzalez
2019-11-19 9:57 ` Russell King - ARM Linux admin
2019-11-19 10:46 ` Marc Gonzalez
2019-11-19 10:56 ` Uwe Kleine-König
2019-11-19 11:00 ` Russell King - ARM Linux admin [this message]
2019-11-19 11:03 ` Uwe Kleine-König
2019-11-19 10:58 ` Russell King - ARM Linux admin
2019-11-19 11:46 ` Marc Gonzalez
2019-11-19 19:19 ` Bjorn Andersson
2019-11-19 19:23 ` Jeffrey Hugo
2019-11-19 19:35 ` Bjorn Andersson
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=20191119110030.GA25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=marc.zyngier@arm.com \
--cc=u.kleine-koenig@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).