From: David Lechner <david@lechnology.com>
To: Sekhar Nori <nsekhar@ti.com>, linux-arm-kernel@lists.infradead.org
Cc: Kevin Hilman <khilman@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: davinci: Allocate extra interrupts
Date: Fri, 20 Jan 2017 12:17:12 -0600 [thread overview]
Message-ID: <dedc276f-e25b-f3b8-dc4a-568f41d9f82e@lechnology.com> (raw)
In-Reply-To: <0bd745dc-df46-0d37-ed18-b419c1cf2e78@ti.com>
On 01/20/2017 05:50 AM, Sekhar Nori wrote:
> On Wednesday 18 January 2017 10:27 PM, David Lechner wrote:
>> On 01/18/2017 03:50 AM, Sekhar Nori wrote:
>>> On Saturday 14 January 2017 01:30 AM, David Lechner wrote:
>>>> This allocates extra interrupts for mach-davinci. These extra interrupts
>>>> are need for things like IIO triggers.
>>>
>>> I am not really familiar with IIO triggers. Can you give some more
>>> detail on what fails without this patch?
>>
>> A trigger is used to initiate the reading of an iio device. For example,
>> there is a mechanism for a sysfs trigger. When you write 1 to the sysfs
>> attribute, it triggers an interrupt that is handled by the iio device.
>>
>> Since these triggers use interrupts, you need to allocate spare
>> interrupts in order to set up the trigger. Otherwise, setting up the
>> trigger will fail with an error code (I forgot which one exactly)
>> because all of the allocated irqs have already been assigned to hardware
>> irqs and are not available.
>>
>> Here is where the iio subsytem actually allocates the irq:
>> http://lxr.free-electrons.com/source/drivers/iio/industrialio-trigger.c#L525
>
> Alright, I will take a look. Do note that this may not get included in
> the first batch of v4.11 changes I queue. But I promise to come back to
> it soon afterwards.
>
It is not critical at this point, so it is fine to wait a bit.
next prev parent reply other threads:[~2017-01-20 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 20:00 [PATCH v2 0/2] ARM: davinci_all_defconfig: enable iio David Lechner
2017-01-13 20:00 ` [PATCH v2 1/2] ARM: davinci: Allocate extra interrupts David Lechner
2017-01-18 9:50 ` Sekhar Nori
2017-01-18 16:57 ` David Lechner
2017-01-20 11:50 ` Sekhar Nori
2017-01-20 18:17 ` David Lechner [this message]
2017-02-02 15:06 ` Sekhar Nori
2017-02-07 19:42 ` David Lechner
2017-01-13 20:00 ` [PATCH v2 2/2] ARM: davinci_all_defconfig: enable iio David Lechner
2017-01-20 11:51 ` Sekhar Nori
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=dedc276f-e25b-f3b8-dc4a-568f41d9f82e@lechnology.com \
--to=david@lechnology.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.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
Powered by JetHome