From: Nishant Sarmukadam <nishants@marvell.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mwl8k: interrupt handling changes
Date: Mon, 11 Apr 2011 11:43:25 +0530 [thread overview]
Message-ID: <1302502405.3447.144.camel@localhost.localdomain> (raw)
In-Reply-To: <20110408181946.GY22881@wantstofly.org>
On Fri, 2011-04-08 at 11:19 -0700, Lennert Buytenhek wrote:
> On Fri, Apr 08, 2011 at 02:38:27PM +0530, Nishant Sarmukadam wrote:
>
> > We do not need to enable all the interrupts in mwl8k_probe_hw.
> > We need to enable only MWL8K_A2H_INT_OPC_DONE interrupt for sending
> > commands to the firmware. Keep the other interrupts masked in
> > mwl8k_probe_hw.
>
> This part of the description matches the patch. But..
>
>
> > Also, in mwl8k_start, where we expect other interrupts,
> > enable only those interrupts we are interested in.
>
> ..this comment does not match the code.
>
>
> > /* Enable interrupts */
> > iowrite32(MWL8K_A2H_EVENTS, priv->regs + MWL8K_HIU_A2H_INTERRUPT_MASK);
> > + iowrite32(MWL8K_A2H_EVENTS,
> > + priv->regs + MWL8K_HIU_A2H_INTERRUPT_STATUS_MASK);
>
> This writes to the status register. Why does it do that?
Here we are writing to the 'status mask' register and not the 'status'
register. Interrupts will not be enabled until we write 1's in the
status mask register. Earlier, we were writing 0xffffffff in this
register, whereas enabling only interrupts specified in MWL8K_A2H_EVENTS
should be sufficient since driver is interested in only those
interrupts. Hence the description.
next prev parent reply other threads:[~2011-04-11 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 9:08 [PATCH] mwl8k: interrupt handling changes Nishant Sarmukadam
2011-04-08 18:19 ` Lennert Buytenhek
2011-04-11 6:13 ` Nishant Sarmukadam [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-08 8:30 Nishant Sarmukadam
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=1302502405.3447.144.camel@localhost.localdomain \
--to=nishants@marvell.com \
--cc=buytenh@wantstofly.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).