Re: [PATCH v4 1/2] gpio/omap: don't create an IRQ mapping for every GPIO on DT

[Alexander Holler <holler@ahsoftware.de>]

Am 29.07.2013 10:17, schrieb Javier Martinez Canillas:
> Hi Alexander,
> 
> On Mon, Jul 29, 2013 at 8:41 AM, Alexander Holler <holler@ahsoftware.de> wrote:
>> Am 28.07.2013 21:06, schrieb Javier Martinez Canillas:
>>
>>> On Sun, Jul 28, 2013 at 8:22 PM, Linus Walleij <linus.walleij@linaro.org>
>>> wrote:
>>>>
>>>> On Sun, Jul 28, 2013 at 7:33 PM, Javier Martinez Canillas
>>>> <martinez.javier@gmail.com> wrote:
>>>>
>>>>> According to Documentation/devicetree/bindings/mmc/mmc.txt:
>>>>>
>>>>> cd-gpios: Specify GPIOs for card detection, see gpio binding
>>>>>
>>>>> So it just says that it is a GPIO for card detection and not an IRQ so
>>>>> this assumption comes from either the omap_hsmmc driver or Alexander'
>>>>> DTS is missing something like:
>>>>>
>>>>>                  interrupt-parent = <&gpio6>;
>>>>>                  interrupts = <16 8>;
>>
>>
>> What do the values 16 and 8 mean here? GPIO numbers?
>> And where do I have to place that?
>>
> 
> If you look at Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
> for the two cells interrupt controllers definition:
> 
>   b) two cells
>   ------------
>   The #interrupt-cells property is set to 2 and the first cell defines the
>   index of the interrupt within the controller, while the second cell is used

I had read that. And there is written, "index of the interrupt". So may
I ask the question how you think people are translating GPIO number to
interrupt index?. And if it's the same, will GPIO0_0 map to IRQ 0 or how
is the magic formular people are supposed to use?

Besides that, the existing standard DTS I've modified into my
"non-standard" dts is arch/arm/boot/dts/am335x-bone.dts.

if you look at the definition of the GPIO bank 0 in
arch/arm/boot/dts/am33xx.dtsi, you see

#interrupt-cells = <1>;

Anyway, thanks for your time, but I don't want to spend more time on
that topic.

Regards,

Alexander Holler