From: david@lechnology.com (David Lechner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] ARM: davinci: convert to common clock framework
Date: Thu, 21 Dec 2017 10:52:58 -0600 [thread overview]
Message-ID: <d196d078-8cd1-01c4-d780-74c7e4a54b8f@lechnology.com> (raw)
In-Reply-To: <d8833055-51ad-a71f-f326-22719cfc1770@ti.com>
On 12/21/2017 06:34 AM, Sekhar Nori wrote:
>
> All I can say is that issue has been noted within TI and I believe
> (hope) that help is on the way!
>
> If we do go the completely separate clock driver route, I think even
> migrating outside of mach-davinci should not be that tough.
>
Based on your responses, I think we have a pretty clear path forward
now. I'm sold on the all at once approach.
If you can pick up the first 3 patches from this series, I have one or
two more I can send that depend on those changes that are not
intermediate steps.
If TI is able to spend some time on this, it would be nice if they could
look at fixing up the reset framework since that is something I haven't
attempted yet.
And I can work on fixing up the PLL and PSC drivers I already have in
drivers/clk/davinci.
next prev parent reply other threads:[~2017-12-21 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 2:15 [PATCH v3 0/5] ARM: davinci: convert to common clock framework David Lechner
2017-12-09 2:15 ` [PATCH v3 1/5] ARM: davinci: move davinci_clk_init() to init_time David Lechner
2017-12-09 2:15 ` [PATCH v3 2/5] ARM: davinci: don't use static clk_lookup David Lechner
2017-12-09 2:15 ` [PATCH v3 3/5] ARM: davinci: make davinci_clk_reset() static David Lechner
2017-12-09 2:15 ` [PATCH v3 4/5] ARM: davinci: convert to common clock framework David Lechner
2017-12-19 13:47 ` Sekhar Nori
2017-12-19 23:12 ` David Lechner
2017-12-21 12:34 ` Sekhar Nori
2017-12-21 16:52 ` David Lechner [this message]
2017-12-26 16:28 ` David Lechner
2017-12-09 2:15 ` [PATCH v3 5/5] ARM: davinci: remove clock debugfs David Lechner
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=d196d078-8cd1-01c4-d780-74c7e4a54b8f@lechnology.com \
--to=david@lechnology.com \
--cc=linux-arm-kernel@lists.infradead.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