From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 1/3] ARM: OMAP2+: hwmod: assign main clock from DT if available
Date: Mon, 29 May 2017 10:07:30 +0300 [thread overview]
Message-ID: <5df79d6b-352d-8341-4bd0-fec4e4cc322d@ti.com> (raw)
In-Reply-To: <20170526154416.GC3717@atomide.com>
On 26/05/17 18:44, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [170518 10:19]:
>> Fix the main clock assignment to assign clkctrl clk from DT as the main
>> clock if available. If main clock is assigned via DT, the direct PRCM
>> access for module handling is not used on OMAP4+ architectures either,
>> as it is assumed the main clock will be doing this instead.
>
> Is this still needed based on what we chatted last week?
>
> I'd like to avoid adding the clkctrl clocks to the wrong node
> as we then end up moving them again later on when we have support
> for the wrapper device..
>
> Regards,
>
> Tony
>
I am investigating this currently, don't have much input yet but an
alternative solution seems rather plausible. If I can get it working, we
don't need this specific patch, but something that will replace it.
-Tero
next prev parent reply other threads:[~2017-05-29 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 17:16 [PATCHv3 0/3] ARM: OMAP2+: preparation for clk/clkctrl support Tero Kristo
2017-05-18 17:16 ` [PATCHv3 1/3] ARM: OMAP2+: hwmod: assign main clock from DT if available Tero Kristo
2017-05-26 15:44 ` Tony Lindgren
2017-05-29 7:07 ` Tero Kristo [this message]
2017-05-18 17:16 ` [PATCHv3 2/3] ARM: OMAP2+: timer: add support for fetching fck handle from DT Tero Kristo
2017-05-18 17:16 ` [PATCHv3 3/3] ARM: OMAP4: hwmod_data: add opt clks for dss_hdmi and dss_venc Tero Kristo
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=5df79d6b-352d-8341-4bd0-fec4e4cc322d@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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