From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC] ARM: shmobile: Disallow PINCTRL without GPIOLIB
Date: Tue, 09 Apr 2013 16:07:58 +0200 [thread overview]
Message-ID: <2575027.16EVpHnJzT@avalon> (raw)
In-Reply-To: <CACRpkdZ9fSoQnF-MgRKi4PUhv56+CuraXhuVgUhLyHcoEnBPZg@mail.gmail.com>
Hi Linus,
On Tuesday 09 April 2013 10:06:45 Linus Walleij wrote:
> On Tue, Mar 26, 2013 at 4:23 PM, Laurent Pinchart wrote:
> >> About this issue, the fact that selecting PINCTRL without GPIO results
> >> in compile error makes me think that something needs slight adjustment
> >> in the PFC code.
> >
> > The above errors come from the pinctrl core (although the PFC driver might
> > not compile either in this case). Linus, what's your opinion on this ? Do
> > we want to support systems with pinctrl but without gpiolib ?
>
> Yes. It is perfectly legal to have pin controllers that do not correlate
> GPIO ranges.
>
> Does commit 2afe8229687ec24cbc07e78449a588bb8b68f858
> "pinctrl: core: add dependence of GPIOLIB"
> by Haojian fix this issue?
Yes it does.
I've just sent a patch that makes GPIOLIB support optional in the PFC driver.
Magnus, with these two, should we revert
6722f6cb763203cab775297b6e9d00834af0d6d7 ?
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-04-09 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 13:58 [PATCH/RFC] ARM: shmobile: Disallow PINCTRL without GPIOLIB Magnus Damm
2013-03-20 13:05 ` Simon Horman
2013-03-20 15:28 ` Laurent Pinchart
2013-03-26 4:04 ` Magnus Damm
2013-03-26 15:23 ` Laurent Pinchart
2013-03-27 11:47 ` Simon Horman
2013-04-09 8:06 ` Linus Walleij
2013-04-09 14:07 ` Laurent Pinchart [this message]
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=2575027.16EVpHnJzT@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox