From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Linus Torvalds <torvalds@g5.osdl.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] UHCI: add missing memory barriers
Date: Sat, 17 Dec 2005 10:58:01 +1100 [thread overview]
Message-ID: <1134777482.6102.9.camel@gaston> (raw)
In-Reply-To: <200512161959.jBGJxh05007356@hera.kernel.org>
On Fri, 2005-12-16 at 11:59 -0800, Linux Kernel Mailing List wrote:
> tree d094f197975af7ef7b80006dbea0f5d38915f88b
> parent 42f3ab42875a52af7e711803bfb8d8d7cca84c1c
> author Alan Stern <stern@rowland.harvard.edu> Sat, 17 Dec 2005 03:09:01 -0800
> committer Linus Torvalds <torvalds@g5.osdl.org> Sat, 17 Dec 2005 03:25:25 -0800
>
> [PATCH] UHCI: add missing memory barriers
>
> This patch (as617) adds a couple of memory barriers that Ben H. forgot in
> his recent suspend/resume fix.
I didn't think they were necessary but they certainly won't hurt and
it's not a hot code path...
> pci_write_config_word(to_pci_dev(uhci_dev(uhci)), USBLEGSUP, 0);
> + mb();
Isn't pci config space access always fully synchronous ?
> clear_bit(HCD_FLAG_HW_ACCESSIBLE, &hcd->flags);
> uhci->hc_inaccessible = 1;
> hcd->poll_rh = 0;
> @@ -738,6 +739,7 @@ static int uhci_resume(struct usb_hcd *h
> * really don't want to keep a stale HCD_FLAG_HW_ACCESSIBLE=0
> */
> set_bit(HCD_FLAG_HW_ACCESSIBLE, &hcd->flags);
> + mb();
I don't think that one matters much but it won't hurt for sure.
> if (uhci->rh_state == UHCI_RH_RESET) /* Dead */
> return 0;
> -
> To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2005-12-17 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200512161959.jBGJxh05007356@hera.kernel.org>
2005-12-16 23:58 ` Benjamin Herrenschmidt [this message]
2005-12-17 3:24 ` Alan Stern
2005-12-17 5:55 ` Benjamin Herrenschmidt
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=1134777482.6102.9.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@g5.osdl.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®