From: Peter Tyser <ptyser@xes-inc.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
linus.walleij@linaro.org, gnurou@gmail.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 2/3] mfd: lpc_ich: use a correct mask for the GPIO base address
Date: Mon, 25 Jan 2016 10:07:50 -0600 [thread overview]
Message-ID: <1453738070.1770.74.camel@xes-inc.com> (raw)
In-Reply-To: <20160125124444.GJ3368@x1>
On Mon, 2016-01-25 at 12:44 +0000, Lee Jones wrote:
> On Sat, 23 Jan 2016, Antoine Tenart wrote:
>
> > The GPIO base address is read from the GPIOBASE register. The first
> > bit must be cleared as it can be hardwired to 1 to represent the i/o
> > space. Other bits are either containing the base address of are
> > reserved. They should not be cleared as all the chipsets do not have
> > the same reserved bits.
> >
> > Signed-off-by: Antoine Tenart tenart@free-electrons.com>
> > ---
> > drivers/mfd/lpc_ich.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
>
> Applied, thanks.
Is it possible to hold off on the application of the change Lee?
> > diff --git a/drivers/mfd/lpc_ich.c b/drivers/mfd/lpc_ich.c
> > index b514f3cf140d..f13a5ded3958 100644
> > --- a/drivers/mfd/lpc_ich.c
> > +++ b/drivers/mfd/lpc_ich.c
> > @@ -921,7 +921,10 @@ static int lpc_ich_init_gpio(struct pci_dev *dev)
> > gpe0_done:
> > /* Setup GPIO base register */
> > pci_read_config_dword(dev, priv->gbase, &base_addr_cfg);
> > - base_addr = base_addr_cfg & 0x0000ff80;
> > +
> > + /* Clear the i/o flag */
> > + base_addr = base_addr_cfg & ~BIT(0);
> > +
Does this patch work around an issue you are seeing? Looking at the Bay
Trail EDS, the GPIO base address register looks like it should work fine
with the original code (it uses 0xff00 as a mask for the address, and
reserves 0x80 which reads as a 0). Also, Bay Trail bit 1 is an enable
flag, which this patch wouldn't mask off. Eg if the BIOS enables the GPIO
controller and sets the enable bit, I think things would break with this
patch.
It's also scary to not mask off the reserved bits on other Intel chipsets -
you're assuming they all read as 0 and I'm not sure if this is true or
not. The patch also doesn't make the same change to the other base
register reads either, and ideally they'd be kept in sync.
Seems like things should be left as-is, or use an accurate chip-specific
mask.
I'd leave as-is personally. Like Mika mentioned, Baytrail GPIO should
already be supported elsewhere, which should make this change unnecessary.
Regards,
Peter
next prev parent reply other threads:[~2016-01-25 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 16:32 [PATCH 0/3] gpio: Intel Baytrail support Antoine Tenart
2016-01-23 16:32 ` [PATCH 1/3] gpio: gpio-ich: add support for Intel Baytrail Antoine Tenart
2016-01-25 12:43 ` Lee Jones
2016-01-23 16:32 ` [PATCH 2/3] mfd: lpc_ich: use a correct mask for the GPIO base address Antoine Tenart
2016-01-25 12:44 ` Lee Jones
2016-01-25 16:07 ` Peter Tyser [this message]
2016-02-11 17:12 ` Lee Jones
2016-01-23 16:32 ` [PATCH 3/3] mfd: lpc_ich: add GPIO support for Baytrail Antoine Tenart
2016-01-25 12:45 ` Lee Jones
2016-01-28 10:34 ` Linus Walleij
2016-01-28 15:48 ` Mika Westerberg
2016-01-25 11:49 ` [PATCH 0/3] gpio: Intel Baytrail support 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=1453738070.1770.74.camel@xes-inc.com \
--to=ptyser@xes-inc.com \
--cc=antoine.tenart@free-electrons.com \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome