From: Andrew Morton <akpm@linux-foundation.org>
To: "Du, Alek" <alek.du@intel.com>
Cc: David Brownell <david-b@pacbell.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: add Penwell gpio support
Date: Thu, 20 May 2010 14:28:21 -0700 [thread overview]
Message-ID: <20100520142821.ed6efd58.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100518154025.4aaff2ee@dxy2>
On Tue, 18 May 2010 15:40:25 +0800
"Du, Alek" <alek.du@intel.com> wrote:
> >From 963f6e83843b0f94f8a5337def6e897ec5bb99bf Mon Sep 17 00:00:00 2001
> From: Alek Du <alek.du@intel.com>
> Date: Thu, 25 Feb 2010 14:32:46 +0800
> Subject: [PATCH] gpio: add Penwell gpio support
>
> Intel Penwell chip has two 96 pins GPIO blocks, which are very similiar as
> Intel Langwell chip GPIO block, except for pin number difference. This
> patch expends the original Langwell GPIO driver to support Penwell's.
>
Has the driver been retested on Moorestown?
> -static int lnw_gpio_get(struct gpio_chip *chip, unsigned offset)
> +static inline void __iomem *gpio_reg(struct gpio_chip *chip, unsigned offset,
> + enum GPIO_REG reg_type)
> {
> struct lnw_gpio *lnw = container_of(chip, struct lnw_gpio, chip);
> + unsigned nreg = chip->ngpio / 32;
> u8 reg = offset / 32;
> - void __iomem *gplr;
> + void __iomem *ptr;
> +
> + ptr = (void __iomem *)(lnw->reg_base + reg_type * nreg * 4 + reg * 4);
> + return ptr;
> +}
inlining this function was probably the wrong thing to do. But modern
gcc's often just ignore the `inline' and do the right thing anyway.
> -static struct pci_device_id lnw_gpio_ids[] = {
> - { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x080f) },
> +static struct pci_device_id lnw_gpio_ids[] = { /* pin number */
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x080f), .driver_data = 64 },
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x081f), .driver_data = 96 },
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x081a), .driver_data = 96 },
> { 0, }
I suppose we should be using DEFINE_PCI_DEVICE_TABLE() here.
next prev parent reply other threads:[~2010-05-20 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 7:40 [PATCH] gpio: add Penwell gpio support Du, Alek
2010-05-20 21:28 ` Andrew Morton [this message]
2010-05-21 3:24 ` Du, Alek
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=20100520142821.ed6efd58.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alek.du@intel.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).