From: "J, KEERTHY" <j-keerthy@ti.com>
To: Sekhar Nori <nsekhar@ti.com>, Bartosz Golaszewski <brgl@bgdev.pl>,
Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
<stable@vger.kernel.org>, Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [PATCH 1/3] ARM: davinci: define gpio interrupts as separate resources
Date: Tue, 20 Nov 2018 12:08:41 +0530 [thread overview]
Message-ID: <63ac671f-b202-2533-3878-af16149fbdbb@ti.com> (raw)
In-Reply-To: <c092b014-d5cf-f1ad-de91-6696b05cdf17@ti.com>
On 11/20/2018 2:22 AM, Sekhar Nori wrote:
> On 13/11/18 7:20 PM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> Since commit eb3744a2dd01 ("gpio: davinci: Do not assume continuous
>> IRQ numbering") the davinci GPIO driver fails to probe if we boot
>> in legacy mode from any of the board files. Since the driver now
>> expects every interrupt to be defined as a separate resource, split
>> the definition in devices-da8xx.c instead of having a single continuous
>> interrupt range.
>>
>> Fixes: eb3744a2dd01 ("gpio: davinci: Do not assume continuous IRQ numbering")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> There are a number of other boards that need such fixing too. And the
> commit in question does not do a good job of explaining why it was
> needed in the first place. The description just repeats what can be
> inferred by reading the patch.
Cc Lokesh
Sekhar,
DT explicitly mentions every IRQ number. The patch in discussion
explicitly calls platform_get_irq for all the interrupts which to me is
the right thing to do as: platform_get_irq-->
of_irq_get-->irq_create_of_mapping--> sequence is to be done for every IRQ.
k3-am654 definitely will need explicit calls to platform_get_irq as it
will be involving interrupt router and interrupt numbers need not be
continuous.
So i do not think reverting the patch is the right idea.
Regards,
Keerthy
>
>
> gpio: davinci: Do not assume continuous IRQ numbering
>
> Currently the driver assumes that the interrupts are continuous
> and does platform_get_irq only once and assumes the rest are continuous,
> instead call platform_get_irq for all the interrupts and store them
> in an array for later use.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>
>
> Can we revert the offending commit instead?
>
> Thanks,
> Sekhar
>
next prev parent reply other threads:[~2018-11-20 6:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 13:50 [PATCH 0/3] ARM: davinci: fix ethernet support on da850-evm Bartosz Golaszewski
2018-11-13 13:50 ` [PATCH 1/3] ARM: davinci: define gpio interrupts as separate resources Bartosz Golaszewski
2018-11-19 20:52 ` Sekhar Nori
2018-11-20 6:38 ` J, KEERTHY [this message]
2018-11-20 23:06 ` Sekhar Nori
2018-11-21 8:51 ` Bartosz Golaszewski
2018-11-13 13:50 ` [PATCH 2/3] gpio: davinci: restore a way to manually specify the GPIO base Bartosz Golaszewski
2018-11-19 13:19 ` Linus Walleij
2018-11-19 14:20 ` Bartosz Golaszewski
2018-11-13 13:50 ` [PATCH 3/3] ARM: davinci: fix da850-evm boot in legacy mode Bartosz Golaszewski
2018-11-19 21:07 ` Sekhar Nori
2018-11-16 21:51 ` [PATCH 0/3] ARM: davinci: fix ethernet support on da850-evm Linus Walleij
2018-11-19 9:11 ` Bartosz Golaszewski
2018-11-20 8:40 ` Linus Walleij
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=63ac671f-b202-2533-3878-af16149fbdbb@ti.com \
--to=j-keerthy@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=grygorii.strashko@ti.com \
--cc=khilman@kernel.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=linux@armlinux.org.uk \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®