linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keerthy <j-keerthy@ti.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] gpio: uniphier: add UniPhier GPIO controller driver
Date: Tue, 8 Aug 2017 09:45:42 +0530	[thread overview]
Message-ID: <059c7046-06cd-fce8-1603-3de7a3dc3d5d@ti.com> (raw)
In-Reply-To: <CAK7LNATCZ9r6KCbFLAW68r9WtYrQ2OvWOZd0AXW4GbdHjHQDVw@mail.gmail.com>



On Tuesday 08 August 2017 06:36 AM, Masahiro Yamada wrote:
> Hi Linus,
> 
> 2017-08-08 0:37 GMT+09:00 Linus Walleij <linus.walleij@linaro.org>:
>> On Mon, Aug 7, 2017 at 3:50 PM, Masahiro Yamada
>> <yamada.masahiro@socionext.com> wrote:
>>
>>> Adding "interrupts" property in DT causes
>>> of_pupulate_default_populate() to assign virtual IRQ numbers
>>> before driver probing.  So it does not work well with IRQ domain hierarchy.
>>
>> I think I heard some noise about this the week before.
>>
>>> For pinctrl/stm32/pinctrl-stm32.c,
>>> I do not see "interrupts", so it just straight maps the irq numbers.
>>
>> I think OMAP and DaVinci does someting similar too. This is from a recent
>> DaVinci patch from Keerthy:
>>
>> +Example for 66AK2G:
>> +
>> +gpio0: gpio@2603000 {
>> +       compatible = "ti,k2g-gpio", "ti,keystone-gpio";
>> +       reg = <0x02603000 0x100>;
>> +       gpio-controller;
>> +       #gpio-cells = <2>;
>> +       interrupts = <GIC_SPI 432 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 433 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 434 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 435 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 436 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 437 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 438 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 439 IRQ_TYPE_EDGE_RISING>,
>> +                       <GIC_SPI 440 IRQ_TYPE_EDGE_RISING>;
>> +       interrupt-controller;
>> +       #interrupt-cells = <2>;
>> +       ti,ngpio = <144>;
>> +       ti,davinci-gpio-unbanked = <0>;
>> +       clocks = <&k2g_clks 0x001b 0x0>;
>> +       clock-names = "gpio";
>> +};
>>
>>
>> That looks fairly similar.
>>
> 
> I do not think so.
> 
> 
> I do not see .alloc hook in drivers/gpio/gpio-davinci.c
> so this driver is unrelated to IRQ domain hierarchy.

Hi Masahiro,

Yes CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled in keystone_defconfig or
davinci_all_defconfig.

Regards,
Keerthy

> 
> 
> 
> 
> 
> 

  reply	other threads:[~2017-08-08  4:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 11:06 [PATCH] gpio: uniphier: add UniPhier GPIO controller driver Masahiro Yamada
     [not found] ` <1501758371-25316-1-git-send-email-yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
2017-08-07 12:42   ` Linus Walleij
     [not found]     ` <CACRpkdZWxjwDnVy5f2rLAWs=+T=5SnwyU8dz1FW1eg8dk8JN_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-07 13:50       ` Masahiro Yamada
2017-08-07 15:37         ` Linus Walleij
2017-08-08  1:06           ` Masahiro Yamada
2017-08-08  4:15             ` Keerthy [this message]
2017-08-11 23:19           ` Masahiro Yamada

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=059c7046-06cd-fce8-1603-3de7a3dc3d5d@ti.com \
    --to=j-keerthy@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).