From: Baruch Siach <baruch@tkos.co.il>
To: Gregory Bean <gbean@codeaurora.org>
Cc: dwalker@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] msm: gpio: Add v2 gpio support to MSM SoCs.
Date: Tue, 16 Nov 2010 07:32:14 +0200 [thread overview]
Message-ID: <20101116053214.GB15652@jasper.tkos.co.il> (raw)
In-Reply-To: <1289852419-7122-1-git-send-email-gbean@codeaurora.org>
Hi Gregory,
On Mon, Nov 15, 2010 at 12:20:18PM -0800, Gregory Bean wrote:
> Beginning with the MSM8x60, the hardware block responsible for gpio
> support changes. Provide gpiolib support for the new v2 architecture.
>
> Cc: Baruch Siach <baruch@tkos.co.il>
> Signed-off-by: Gregory Bean <gbean@codeaurora.org>
> ---
[snip]
> +struct msm_gpio_dev {
> + struct gpio_chip gpio_chip;
> +};
This wrapper struct seems redundant. You only use it in msm_gpio_probe, where
you can just use 'struct gpio_chip' directly.
> +static DEFINE_SPINLOCK(tlmm_lock);
> +
> +static inline struct msm_gpio_dev *to_msm_gpio_dev(struct gpio_chip *chip)
> +{
> + return container_of(chip, struct msm_gpio_dev, gpio_chip);
> +}
Not used.
> +static inline void set_gpio_bits(unsigned n, void __iomem *reg)
> +{
> + writel(readl(reg) | n, reg);
> +}
Move the locking in, or better, eliminate it, since it's only used in
msm_gpio_direction_output.
[snip]
> +static struct platform_device msm_device_gpio = {
> + .name = "msmgpio",
> + .id = 0,
Redundant.
> +};
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2010-11-16 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 20:20 Gregory Bean
2010-11-15 20:20 ` [PATCH v2 2/2] msm: gpio: Add irq support to v2 gpiolib Gregory Bean
2010-11-16 5:32 ` Baruch Siach [this message]
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=20101116053214.GB15652@jasper.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=dwalker@codeaurora.org \
--cc=gbean@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--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®