From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: ralf@linux-mips.org, john@phrozen.org, linux-mips@linux-mips.org,
linux-wireless@vger.kernel.org, florian@openwrt.org
Subject: Re: [PATCH v3 2/3] bcma: add GPIO driver for SoCs
Date: Sun, 09 Sep 2012 17:22:06 +0200 [thread overview]
Message-ID: <504CB41E.6070201@hauke-m.de> (raw)
In-Reply-To: <CACna6rwb15pfbM6rM5ros0yCSW+uv1CbwWz5pUz8OgvONKKrvg@mail.gmail.com>
On 09/03/2012 09:15 PM, Rafał Miłecki wrote:
> 2012/8/31 Hauke Mehrtens <hauke@hauke-m.de>:
>> +u32 bcma_gpio_in(struct bcma_bus *bus, u32 mask)
>> +{
>> + unsigned long flags;
>> + u32 res = 0;
>> +
>> + spin_lock_irqsave(&bus->gpio_lock, flags);
>> + res = bcma_chipco_gpio_in(&bus->drv_cc, mask);
>> + spin_unlock_irqrestore(&bus->gpio_lock, flags);
>> +
>> + return res;
>> +}
>> +EXPORT_SYMBOL(bcma_gpio_in);
>
>
> Could we put here direct ops on ChipCommon regs and drop GPIO
> functions from driver_chipcommon.c?
So you mean that all accesses to the gpio registers are locked, also
when b43 or bcma accesses them? If so, I will change my patch and test
it on my devices. I am currently not at my development machine and do
not have the test devices here, but I will see if I find some time on
Tuesday when I am home again.
So bcma_chipco_gpio_XXX() should not be exported in the way it is done
now any more and all accesses to the gpio registers should be locked.
Hauke
next prev parent reply other threads:[~2012-09-09 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 15:38 [PATCH v3 0/3] MIPS: BCM47xx: use gpiolib Hauke Mehrtens
2012-08-31 15:38 ` [PATCH v3 1/3] ssb: add function to return number of gpio lines Hauke Mehrtens
2012-08-31 15:38 ` [PATCH v3 2/3] bcma: add GPIO driver for SoCs Hauke Mehrtens
2012-09-03 19:15 ` Rafał Miłecki
2012-09-09 15:22 ` Hauke Mehrtens [this message]
2012-08-31 15:38 ` [PATCH v3 3/3] MIPS: BCM47xx: rewrite GPIO handling and use gpiolib Hauke Mehrtens
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=504CB41E.6070201@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=florian@openwrt.org \
--cc=john@phrozen.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=zajec5@gmail.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