From: Jean Delvare <jdelvare@suse.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-gpio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [PATCH RESEND] pinctrl: intel: Turn Baytrail support to tristate
Date: Fri, 27 Jan 2017 09:55:53 +0100 [thread overview]
Message-ID: <20170127095553.02cbd9ad@endymion> (raw)
In-Reply-To: <20170126092911.GF17297@lahna.fi.intel.com>
On Thu, 26 Jan 2017 11:29:11 +0200, Mika Westerberg wrote:
> On Thu, Jan 26, 2017 at 10:05:06AM +0100, Jean Delvare wrote:
> > I have not, as I do not have access to any Baytrail hardware. This is
> > the very reason why I'd like this code to be buildable as a module: I'm
> > not happy with a useless 50 kB driver being loaded on all my systems. I
> > was hopping someone at Intel would have access to the hardware to
> > perform the test.
>
> We do not have all the possible hardware here. I have one Minnowboard
> MAX which I can test this on (like I commented in the other email) but
> it does not have any ACPI GPIO OpRegion stuff that is present in many
> Baytrail based laptops out there.
Takashi, do you have any such laptop or know anyone at SUSE who does
and could test?
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2017-01-27 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 15:26 [PATCH RESEND] pinctrl: intel: Turn Baytrail support to tristate Jean Delvare
2017-01-25 16:15 ` Andy Shevchenko
2017-01-25 16:16 ` Mika Westerberg
2017-01-26 9:05 ` Jean Delvare
2017-01-26 9:29 ` Mika Westerberg
2017-01-27 8:55 ` Jean Delvare [this message]
2017-01-26 8:37 ` Heikki Krogerus
2017-01-26 8:55 ` Linus Walleij
2017-01-26 9:19 ` Mika Westerberg
2017-01-26 9:26 ` Takashi Iwai
2017-01-26 9:38 ` Mika Westerberg
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=20170127095553.02cbd9ad@endymion \
--to=jdelvare@suse.de \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=paul.gortmaker@windriver.com \
--cc=tiwai@suse.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 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.