From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Peter Robinson <pbrobinson@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] pinctrl: intel: wrap Intel pin control drivers in an architecture check
Date: Tue, 04 Jul 2017 13:21:13 +0300 [thread overview]
Message-ID: <1499163673.22624.248.camel@linux.intel.com> (raw)
In-Reply-To: <20170704095459.GB1250@kuha.fi.intel.com>
On Tue, 2017-07-04 at 12:54 +0300, Heikki Krogerus wrote:
> On Tue, Jul 04, 2017 at 07:49:47AM +0100, Peter Robinson wrote:
> > The Intel pin control drivers are architecture specific so add an if
> > arch
> > to check for X86 or compile test to ensure continued test coverage.
> >
Sorry, have not seen the original mail.
> > Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> > Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> > ---
> > drivers/pinctrl/intel/Kconfig | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/pinctrl/intel/Kconfig
> > b/drivers/pinctrl/intel/Kconfig
> > index 396830a41127..0c7edc321415 100644
> > --- a/drivers/pinctrl/intel/Kconfig
> > +++ b/drivers/pinctrl/intel/Kconfig
> > @@ -1,6 +1,7 @@
> > #
> > # Intel pin control drivers
> > #
> > +if (X86 || COMPILE_TEST)
And what about ARM et al. architectures?
Instead I would propose to reorganize parent Kconfig to have something
like
if (ARM || COMPILE_TEST)
...ARM stuff...
endif
if (X86 || COMPILE_TEST)
...X86 stuff...
endif
But personally I don't like any of the above. So, what's the issue this
patch is targeting against?
> >
> > config PINCTRL_BAYTRAIL
> > bool "Intel Baytrail GPIO pin control"
> > @@ -72,3 +73,5 @@ config PINCTRL_SUNRISEPOINT
> > Sunrisepoint is the PCH of Intel Skylake. This pinctrl
> > driver
> > provides an interface that allows configuring of PCH pins
> > and
> > using them as GPIOs.
> > +
> > +endif
>
> OK by me:
>
> Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>
>
> Thanks,
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-07-04 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 6:49 [PATCH] pinctrl: intel: wrap Intel pin control drivers in an architecture check Peter Robinson
2017-07-04 9:54 ` Heikki Krogerus
2017-07-04 10:21 ` Andy Shevchenko [this message]
2017-07-05 8:01 ` Peter Robinson
2017-08-29 13:49 ` Andy Shevchenko
2017-07-31 13:41 ` Linus Walleij
2017-07-31 13:48 ` Mika Westerberg
2017-08-07 8:47 ` Linus Walleij
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=1499163673.22624.248.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pbrobinson@gmail.com \
/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.