From: Sekhar Nori <nsekhar@ti.com>
To: Olof Johansson <olof@lixom.net>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
ARM-SoC Maintainers <arm@kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [GIT PULL] DaVinci fixes for v4.20
Date: Mon, 3 Dec 2018 15:59:00 +0530 [thread overview]
Message-ID: <62333206-5e21-195c-ef57-ab8c1ed0bccb@ti.com> (raw)
In-Reply-To: <20181130195516.t53j6ui7szcvq6uf@localhost>
Hi Olof,
On 01/12/18 1:25 AM, Olof Johansson wrote:
> On Tue, Nov 27, 2018 at 05:48:28PM +0530, Sekhar Nori wrote:
>> The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
>>
>> Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
>>
>> are available in the Git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-fixes-for-v4.20
>>
>> for you to fetch changes up to 27df7977099c2b8d32399cd1752f527c5a343dfa:
>>
>> ARM: davinci: dm644x: set the GPIO base to 0 (2018-11-27 13:43:27 +0530)
>>
>> ----------------------------------------------------------------
>> DaVinci: fix GPIO breakage after v4.19
>>
>> This set of changes is needed to fix the broken GPIO support
>> for DaVinci boards in legacy mode after certain changes made to the
>> GPIO driver in 4.19, namely: commits 587f7a694f01 ("gpio: davinci: Use
>> dev name for label and automatic base selection") and eb3744a2dd01
>> ("gpio: davinci: Do not assume continuous IRQ numbering").
>
> Hm. How long until we can remove the legacy boards and move them to DT? Is
> anyone working on it?
I think we are a bit far from that. The limited resources available to
work on DaVinci are being used to update frameworks. We moved to common
clock framework this year across all 6 supported SoCs. My plan for next
year is to move to sparse IRQ and get DaVinci included in
multi_v5_defconfig. Also move timer drivers to clocksource.
Even in cases where we do have device-tree support for the SoC (like
DA850), getting rid of board files completely involves writing some
additional drivers for board specific functionality. This I think is the
main bottleneck.
But I have not given up on getting there completely. The progress is
slow, though.
Thanks,
Sekhar
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-03 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 12:18 [GIT PULL] DaVinci fixes for v4.20 Sekhar Nori
2018-11-30 19:55 ` Olof Johansson
2018-12-03 10:29 ` Sekhar Nori [this message]
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=62333206-5e21-195c-ef57-ab8c1ed0bccb@ti.com \
--to=nsekhar@ti.com \
--cc=arm@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
/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