From: "Yang,Wei" <Wei.Yang@windriver.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: <mroberto@cpti.cetuc.puc-rio.br>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1] ARM:sa1100: Remove a redundant spin lock
Date: Wed, 2 Jul 2014 19:02:12 +0800 [thread overview]
Message-ID: <53B3E6B4.2040907@windriver.com> (raw)
In-Reply-To: <20140702101925.GE32514@n2100.arm.linux.org.uk>
On 07/02/2014 06:19 PM, Russell King - ARM Linux wrote:
> On Wed, Jul 02, 2014 at 05:19:40PM +0800, Yang,Wei wrote:
>> Hi Guys,
>>
>> What about this patch?
> The only concern on the face of it is that it removes mutual exclusion
> from the pci config write path, where a read-modifiy-write operation is
> performed.
>
> However, the PCI code already gives that guarantee (drivers/pci/access.c)
> so this should be safe.
>
> As this is fairly old code, it would be useful to know what the motivation
> is behind this change. Is it purely clean up, or is it something that
> you've tested, or is this a change that you require for something else?
>
> Thanks.
>
Hmm, I fixed a bug of pci config read/write of an ARM board, but
unfortunately, so far ML does not support it. So
I cannot send the fix, but I grepped the pci source code of ARM
architecure, I found that the pci code of a few boards always
define a static spin lock to excluse the pci config read/write path. I
just intended to clean up them. If you agree the change,
I want to send v2 to also remove this mutual exclusion for something
else board which also used the mutual exclusion.
Thanks
Wei
prev parent reply other threads:[~2014-07-02 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 7:41 [PATCH v1] ARM:sa1100: Remove a redundant spin lock Wei.Yang
2014-07-02 9:19 ` Yang,Wei
2014-07-02 10:19 ` Russell King - ARM Linux
2014-07-02 11:02 ` Yang,Wei [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=53B3E6B4.2040907@windriver.com \
--to=wei.yang@windriver.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mroberto@cpti.cetuc.puc-rio.br \
/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