From: Grant Likely <grant.likely@secretlab.ca>
To: Linus Walleij <linus.walleij@linaro.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: add a driver for GPIO pins found on AMD-8111 south bridge chips
Date: Fri, 18 May 2012 16:35:32 -0600 [thread overview]
Message-ID: <20120518223532.7029B3E07C8@localhost> (raw)
In-Reply-To: <CACRpkdZbr9CvCWx_a2Cf1MiJE_FDLQM4qipqRbnTRw+jM8U7gA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]
On Fri, 27 Apr 2012 12:52:19 +0200, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Fri, Apr 27, 2012 at 12:08 PM, Dmitry Eremin-Solenikov
> <dbaryshkov@gmail.com> wrote:
>
> > Add a driver to use GPIO pins available on several AMD south bridges
> > (currently only AMD 8111 is supported).
> >
> > Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
>
> Mainly nitpicks, it's looking good overall...
Hi Dimtry,
Do you have an updated version of this patch to address Linus' comments?
g.
>
> > + spin_lock_irqsave(&agp->lock, flags);
> > + temp = ioread8(agp->pm - PMBASE_OFFSET + PMBASE_GPIO(offset));
> > + temp = (temp & 0x1c) | (!!value);
>
> This is a bit idomatic but I think I understand what's going on. However this
> 0x1C magic could be better of with some #define AMD_8111_GPIO_FOO don't
> you think?
>
> > +static int amd_gpio_get(struct gpio_chip *chip, unsigned offset)
> > +{
> > + struct amd_gpio *agp = to_agp(chip);
> > + u8 temp;
> > +
> > + temp = ioread8(agp->pm - PMBASE_OFFSET + PMBASE_GPIO(offset));
> > +
> > + dev_dbg(&agp->pdev->dev, "Getting gpio %d, reg=%02x\n", offset, temp);
> > +
> > + return !!(temp & 0x20);
>
> And this could be #define AMD_8111_GPIO_INVAL or so (I bet this bit has a
> name in the datasheet, right?)
>
> > +static int amd_gpio_dirout(struct gpio_chip *chip, unsigned offset, int value)
> > +{
> > + struct amd_gpio *agp = to_agp(chip);
> > + u8 temp;
> > + unsigned long flags;
> > +
> > + spin_lock_irqsave(&agp->lock, flags);
> > + temp = ioread8(agp->pm - PMBASE_OFFSET + PMBASE_GPIO(offset));
> > + temp = (temp & 0x10) | 0x4 | (!!value);
>
> And so on...
>
> > + iowrite8(temp, agp->pm - PMBASE_OFFSET + PMBASE_GPIO(offset));
> > + spin_unlock_irqrestore(&agp->lock, flags);
> > +
> > + dev_dbg(&agp->pdev->dev, "Dirout gpio %d, value %d, reg=%02x\n", offset, !!value, temp);
> > +
> > + return 0;
> > +}
>
> > +static int __init mod_init(void)
>
> amd_gpio_init() maybe? These names are nice for e.g. ftrace.
>
> > + printk(KERN_INFO "AMD-8111 GPIO detected\n");
>
> pr_info() & friends are nice shorthands for this.
>
> > +static void __exit mod_exit(void)
>
> amd_gpio_mod_exit()?
>
> > +MODULE_AUTHOR("The Linux Kernel team");
>
> Don't be shy, put in your own name :-)
>
> Yours,
> Linus Walleij
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
next prev parent reply other threads:[~2012-05-18 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 10:08 Dmitry Eremin-Solenikov
2012-04-27 10:52 ` Linus Walleij
2012-05-18 22:35 ` Grant Likely [this message]
2012-05-18 22:43 ` Dmitry Eremin-Solenikov
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=20120518223532.7029B3E07C8@localhost \
--to=grant.likely@secretlab.ca \
--cc=dbaryshkov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--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
all inboxes | Powered by JetHome®