Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1411462 > unrolled thread
| Started by | Dmitry Torokhov <dmitry.torokhov@gmail.com> |
|---|---|
| First post | 2016-06-01 20:40 +0200 |
| Last post | 2016-06-01 20:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 3/3] input: touchscreen: mxs-lradc: Add support for touchscreen Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2016-06-01 20:40 +0200
| From | Dmitry Torokhov <dmitry.torokhov@gmail.com> |
|---|---|
| Date | 2016-06-01 20:40 +0200 |
| Subject | Re: [PATCH 3/3] input: touchscreen: mxs-lradc: Add support for touchscreen |
| Message-ID | <rFjdE-3CV-17@gated-at.bofh.it> |
On Sat, May 28, 2016 at 07:46:07PM +0200, Ksenija Stanojević wrote:
> On Sat, Apr 30, 2016 at 1:36 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > Hi Ksenija,
> >
> > On Fri, Apr 29, 2016 at 01:49:11PM +0200, Ksenija Stanojevic wrote:
> >> +
> >> + mxs_lradc_ts_hw_init(ts);
> >> + for (i = 0; i < lradc->irq_count; i++) {
> >> + ret = devm_request_irq(dev, lradc->irq[i],
> >> + mxs_lradc_ts_handle_irq,
> >
> > Hmm, if you have several interrupts handled by the same interrupt
> > handler you'd need some locking there.
>
> same interrupt handler can run concurrently only on multi cores, so
> why do we need locking?
We do not necessarily need it on single core (unless someone will turn
it int threaded IRQ down the road), but adding it costs almost nothing
and will ensure that the driver will continue working even if block is
moved to multi-core SOC in the future...
Thanks.
--
Dmitry
Back to top | Article view | linux.kernel
csiph-web