From: <Lukasz.Rymanowski@tieto.com>
To: <tglx@linutronix.de>, <par-gunnar.p.hjalmdahl@stericsson.com>
Cc: <gregkh@suse.de>, <devel@driverdev.osuosl.org>,
<linus.walleij@linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-bluetooth@vger.kernel.org>, <pavan_savoy@sify.com>,
<vitalywool@gmail.com>, <alan@lxorguk.ukuu.org.uk>,
<arnd@arndb.de>, <marcel@holtmann.org>,
<linus.walleij@stericsson.com>, <pghatwork@gmail.com>,
<lee.jones@linaro.org>, <mathieu.poirier@linaro.org>
Subject: RE: [PATCH v2 1/2] staging: Add ST-Ericsson CG2900 driver
Date: Mon, 28 Mar 2011 13:05:35 +0300 [thread overview]
Message-ID: <7D7F2FD3846CF6429ACEBDFB5A2DD86F07E35E5F89@EXMB01.eu.tieto.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1103281110210.31464@localhost6.localdomain6>
>> +/**
>> + * cts_interrupt() - Called to handle CTS interrupt.
>> + * @irq: Interrupt that occurred.
>> + * @dev_id: Device ID where interrupt occurred.
>> + *
>> + * The cts_interrupt() function is called if interrupt on CTS occurred.
>> + * It disables the interrupt and starts a new work thread to handle
>> + * the interrupt.
>> + */
>> +static irqreturn_t cts_interrupt(int irq, void *dev_id) {
>> + struct uart_info *uart_info = dev_get_drvdata(dev_id); #ifdef
>> +CONFIG_PM
>> + disable_irq_wake(irq);
>> +#endif
>> + disable_irq_nosync(irq);
>> +
>> + /* Create work and leave IRQ context. */
>> + (void)create_work_item(uart_info, handle_cts_irq);
>> +
>> + return IRQ_HANDLED;
>> +}
>Have you thought about using a threaded interrupt handler? That would make all this work cruft go away.
Good point.
To be honest we did think about it but in the time we where we were busy with other issues.
Anyway, shall we resend patches now or we can push patch for it once driver gets in the tree ?
/Lukasz
>Thanks,
> tglx
next prev parent reply other threads:[~2011-03-28 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 9:02 Par-Gunnar Hjalmdahl
2011-03-28 9:13 ` Thomas Gleixner
2011-03-28 10:05 ` Lukasz.Rymanowski [this message]
2011-03-28 10:21 ` Thomas Gleixner
2011-03-28 14:11 ` Greg KH
2011-03-28 13:02 ` Arnd Bergmann
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=7D7F2FD3846CF6429ACEBDFB5A2DD86F07E35E5F89@EXMB01.eu.tieto.com \
--to=lukasz.rymanowski@tieto.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mathieu.poirier@linaro.org \
--cc=par-gunnar.p.hjalmdahl@stericsson.com \
--cc=pavan_savoy@sify.com \
--cc=pghatwork@gmail.com \
--cc=tglx@linutronix.de \
--cc=vitalywool@gmail.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
all inboxes | Powered by JetHome®