From: Felipe Balbi <balbi@ti.com>
To: Andreas Larsson <andreas@gaisler.com>
Cc: balbi@ti.com, linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
software@gaisler.com
Subject: Re: [PATCH v3] usb: gadget: Add UDC driver for Aeroflex Gaisler GRUSBDC
Date: Mon, 16 Dec 2013 15:25:51 -0600 [thread overview]
Message-ID: <20131216212551.GG12896@saruman.home> (raw)
In-Reply-To: <52AE2C0C.80401@gaisler.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hi,
On Sun, Dec 15, 2013 at 11:24:12PM +0100, Andreas Larsson wrote:
> >>>Also, the way you're using thread IRQs is quite wrong. I can't let that
> >>>pass and get merged upstream, sorry.
> >>
> >>What is quite wrong? What is it that I need to fix?
> >
> >Ideally the hardirq handler should be usually to actually check if
> >$this_device generated the IRQ, that should involve reading a IRQSTATUS
> >register of some sort.
> >
> >Sure, check that IRQs are actually enabled, but you also need to read
> >STATUS register before waking the thread up.
>
> I agree that that would be preferable. Unfortunately, the hardware
> lacks status register bits that indicates whether interrupts has been
> generated or not. That is why the only check is if interrupts are
> disabled, because that is the only sure way to know that the softirq
> handler does not need to go through everything.
so it seems, fair enough then. Keep it the way it is.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-12-16 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 8:13 [PATCH v3] usb: gadget: Add UDC driver for Aeroflex Gaisler GRUSBDC Andreas Larsson
2013-12-12 18:01 ` Felipe Balbi
2013-12-13 7:48 ` Andreas Larsson
2013-12-13 19:52 ` Felipe Balbi
[not found] ` <20131213195234.GE5292-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2013-12-15 22:24 ` Andreas Larsson
2013-12-16 21:25 ` Felipe Balbi [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=20131216212551.GG12896@saruman.home \
--to=balbi@ti.com \
--cc=andreas@gaisler.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=software@gaisler.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;
as well as URLs for NNTP newsgroup(s).