From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v5 1/4] ath9k: implement IO serialization
Date: Wed, 11 Mar 2009 09:07:40 -0700 [thread overview]
Message-ID: <20090311160740.GB5669@tesla> (raw)
In-Reply-To: <1236762611.9658.87.camel@johannes.local>
On Wed, Mar 11, 2009 at 02:10:11AM -0700, Johannes Berg wrote:
> On Tue, 2009-03-10 at 22:52 -0400, Luis R. Rodriguez wrote:
>
> > + if (ah->config.serialize_regmode == SER_REG_MODE_ON) {
> > + unsigned long flags;
> > + spin_lock_irqsave(&ah->ah_sc->sc_serial_rw, flags);
> > + iowrite32(val, ah->ah_sc->mem + reg_offset);
> > + spin_unlock_irqrestore(&ah->ah_sc->sc_serial_rw, flags);
> > + } else
> > + iowrite32(val, ah->ah_sc->mem + reg_offset);
>
> This is utterly insane. Just make it _always_ do the spinlock, and get
> rid of the hotplug notifier and all that crap.
That is certainly an option as well but we would obviously be incurring
the lock on all reads/writes regardless of what bus you use which is
not necessary. We'll review this and determine whether its worth it.
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v5 1/4] ath9k: implement IO serialization
Date: Wed, 11 Mar 2009 09:07:40 -0700 [thread overview]
Message-ID: <20090311160740.GB5669@tesla> (raw)
In-Reply-To: <1236762611.9658.87.camel@johannes.local>
On Wed, Mar 11, 2009 at 02:10:11AM -0700, Johannes Berg wrote:
> On Tue, 2009-03-10 at 22:52 -0400, Luis R. Rodriguez wrote:
>
> > + if (ah->config.serialize_regmode == SER_REG_MODE_ON) {
> > + unsigned long flags;
> > + spin_lock_irqsave(&ah->ah_sc->sc_serial_rw, flags);
> > + iowrite32(val, ah->ah_sc->mem + reg_offset);
> > + spin_unlock_irqrestore(&ah->ah_sc->sc_serial_rw, flags);
> > + } else
> > + iowrite32(val, ah->ah_sc->mem + reg_offset);
>
> This is utterly insane. Just make it _always_ do the spinlock, and get
> rid of the hotplug notifier and all that crap.
That is certainly an option as well but we would obviously be incurring
the lock on all reads/writes regardless of what bus you use which is
not necessary. We'll review this and determine whether its worth it.
Luis
next prev parent reply other threads:[~2009-03-11 16:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 2:52 [ath9k-devel] [PATCH v5 0/4] ath9k: SMP fixes Luis R. Rodriguez
2009-03-11 2:52 ` Luis R. Rodriguez
2009-03-11 2:52 ` [ath9k-devel] [PATCH v5 1/4] ath9k: implement IO serialization Luis R. Rodriguez
2009-03-11 2:52 ` Luis R. Rodriguez
2009-03-11 9:10 ` [ath9k-devel] " Johannes Berg
2009-03-11 9:10 ` Johannes Berg
2009-03-11 16:07 ` Luis R. Rodriguez [this message]
2009-03-11 16:07 ` Luis R. Rodriguez
2009-03-11 17:13 ` [ath9k-devel] " Johannes Berg
2009-03-11 17:13 ` Johannes Berg
2009-03-11 17:20 ` [ath9k-devel] " Luis R. Rodriguez
2009-03-11 17:20 ` Luis R. Rodriguez
2009-03-11 17:30 ` Johannes Berg
2009-03-11 17:30 ` Johannes Berg
2009-03-11 21:08 ` Luis R. Rodriguez
2009-03-11 21:08 ` Luis R. Rodriguez
2009-03-11 21:38 ` Christian Lamparter
2009-03-11 21:38 ` Christian Lamparter
2009-03-11 20:51 ` Luis R. Rodriguez
2009-03-11 20:51 ` Luis R. Rodriguez
2009-03-11 2:52 ` [ath9k-devel] [PATCH v5 2/4] ath9k: AR9280 PCI devices must serialize IO as well Luis R. Rodriguez
2009-03-11 2:52 ` Luis R. Rodriguez
2009-03-11 2:52 ` [ath9k-devel] [PATCH v5 3/4] ath9k: add cpu notifier to enhance device configuration Luis R. Rodriguez
2009-03-11 2:52 ` Luis R. Rodriguez
2009-03-11 2:52 ` [ath9k-devel] [PATCH v5 4/4] ath9k: remove dummy PCI "retry timeout" fix Luis R. Rodriguez
2009-03-11 2:52 ` Luis R. Rodriguez
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=20090311160740.GB5669@tesla \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.