[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8cf84d9f-e9d9-4c18-ac0b-e568a34f2608@posteo.de>
Date: Tue, 22 Oct 2019 15:08:37 +0200
From: Martin Kepplinger <martink@...teo.de>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Andrey Smirnov <andrew.smirnov@...il.com>,
linux-iio@...r.kernel.org, Chris Healy <cphealy@...il.com>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: mma8452: Re-word 'interrupt-names'
description
On 22.10.19 12:50, Jonathan Cameron wrote:
> On Tue, 22 Oct 2019 10:43:09 +0200
> Martin Kepplinger <martink@...teo.de> wrote:
>
>> On 22.10.19 05:56, Andrey Smirnov wrote:
>>> Current wording in the binding documentation doesn't make it 100%
>>> clear that only one of "INT1" and "INT2" will ever be used by the
>>> driver and that specifying both has no advantages. Re-word it to make
>>> this aspect a bit more explicit.
>
> From a quick glance at the datasheet, it appears that the hardware
> is capable of routing different interrupts to different pins, even
> if the driver does not do so.
>
> CTRL_REG5 has 6 different bits to set whether particular blocks have
> their interrupt routed to INT1 or INT2, so it appears to be possible
> to send some each way.
>
> A binding is for the hardware not the driver, so if I'm right about this
> the current text is correct and should be left alone.
right, please ignore my "acked-by". Thanks a lot for taking a look.
martin
Powered by blists - more mailing lists