devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: tony@atomide.com, paul@pwsan.com, mturquette@baylibre.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCHv2 00/28] ARM: OMAP2+: hwmod module clock type support
Date: Thu, 12 May 2016 16:39:35 -0700	[thread overview]
Message-ID: <20160512233935.GN3492@codeaurora.org> (raw)
In-Reply-To: <1460632097-25727-1-git-send-email-t-kristo@ti.com>

On 04/14, Tero Kristo wrote:
> Hi,
> 
> v2 contains following changes in comparison to v1:
> 
> - Patch ordering changed a bit, clk/ti, mach-omap2, dts patches are now
>   mostly grouped together, with the exception of the introduction of
>   clock helper API, which is needed by everything else. Please note
>   that the ordering must be preserved between mach-omap2/clk-driver/dts
>   to avoid boot problems.
> - Dropped hwmod data removal patches for now, this allows booting with
>   either new or old DTS data.
> - Fixed a typo in the hwmod clock driver timeout handling, the comparison
>   for timeout against ktime_us_delta was wrong causing too short
>   timeouts, this was apparent with cpuidle enabled on OMAP4
> - Added patch #6 to fetch hwmod main clock based on the hwmod name itself,
>   if found, ignore main_clk / clkctrl setup for the hwmod
> - Added patch #7 to fix issue in omap2 timer caused by patch #6, with
>   dynamic parsing of main clock, the hwmod must be setup before attempting
>   to access main_clk.

What's the general design goal of this series? This cover letter
is more like a change and test log instead of an overall argument
for why the series should be merged so I'm left to piecing
together the commit text from the 28 different patches. I suspect
it's to get rid of DT_CLK macros and do something with hwmod in a
more generic way, but that's all I got.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2016-05-12 23:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 11:07 [PATCHv2 00/28] ARM: OMAP2+: hwmod module clock type support Tero Kristo
2016-04-14 11:07 ` [PATCHv2 02/28] clk: ti: dpll: use ti_clk_get to fetch ref/bypass clocks Tero Kristo
2016-04-14 11:07 ` [PATCHv2 03/28] ARM: OMAP2+: omap_device: create clock alias purely from DT data Tero Kristo
2016-04-14 11:07 ` [PATCHv2 04/28] ARM: OMAP2+: hwmod: use new ti_clk_get API to search for clock handles Tero Kristo
2016-04-14 11:07 ` [PATCHv2 06/28] ARM: OMAP2+: hwmod: fetch main_clk based on hwmod name Tero Kristo
2016-04-14 11:07 ` [PATCHv2 07/28] ARM: OMAP2+: timer: change order of hwmod data handling Tero Kristo
     [not found] ` <1460632097-25727-1-git-send-email-t-kristo-l0cyMroinI0@public.gmane.org>
2016-04-14 11:07   ` [PATCHv2 01/28] clk: ti: add ti_clk_get helper API Tero Kristo
2016-04-14 11:07   ` [PATCHv2 05/28] ARM: OMAP2+: clock: use the new ti_clk_get for fetching clocks Tero Kristo
2016-04-14 11:07   ` [PATCHv2 08/28] ARM: OMAP2+: clockdomain: add usecounting support to autoidle APIs Tero Kristo
2016-04-14 11:07   ` [PATCHv2 09/28] ARM: AM33xx: fix module_wait_ready without clkctrl register Tero Kristo
2016-04-14 11:07   ` [PATCHv2 10/28] clk: ti: omap2: transition to usage of ti_clk_get Tero Kristo
2016-04-14 11:08   ` [PATCHv2 11/28] clk: ti: am33xx: " Tero Kristo
2016-04-14 11:08   ` [PATCHv2 12/28] clk: ti: omap3: " Tero Kristo
2016-04-14 11:08   ` [PATCHv2 13/28] clk: ti: am43xx: " Tero Kristo
2016-04-14 11:08   ` [PATCHv2 14/28] clk: ti: omap4: " Tero Kristo
2016-04-14 11:08   ` [PATCHv2 20/28] clk: ti: mux: export mux clock APIs locally Tero Kristo
2016-04-14 11:08   ` [PATCHv2 21/28] clk: ti: am33xx: fix timer3/6 init time setup for module clocks Tero Kristo
2016-04-14 11:08   ` [PATCHv2 24/28] ARM: dts: omap4: add hwmod " Tero Kristo
2016-04-14 11:08   ` [PATCHv2 26/28] ARM: dts: am43xx: " Tero Kristo
2016-04-14 11:08   ` [PATCHv2 27/28] ARM: dts: omap5: " Tero Kristo
2016-04-14 11:08 ` [PATCHv2 15/28] clk: ti: omap5: transition to usage of ti_clk_get Tero Kristo
2016-04-14 11:08 ` [PATCHv2 16/28] clk: ti: dra7: " Tero Kristo
2016-04-14 11:08 ` [PATCHv2 17/28] clk: ti: dm814x: " Tero Kristo
2016-04-14 11:08 ` [PATCHv2 18/28] clk: ti: dm816x: cleanup any unnecessary clock aliases Tero Kristo
2016-04-14 11:08 ` [PATCHv2 19/28] clk: ti: remove un-used definitions from public clk_hw_omap struct Tero Kristo
2016-04-14 11:08 ` [PATCHv2 22/28] dt-bindings: clk: ti: Document module clock type Tero Kristo
2016-04-14 11:08 ` [PATCHv2 23/28] clk: ti: add support for omap4 module clocks Tero Kristo
2016-04-14 11:08 ` [PATCHv2 25/28] ARM: dts: am33xx: add hwmod " Tero Kristo
2016-04-14 11:08 ` [PATCHv2 28/28] ARM: dts: dra7: " Tero Kristo
2016-05-12 23:39 ` Stephen Boyd [this message]
2016-05-13 10:58   ` [PATCHv2 00/28] ARM: OMAP2+: hwmod module clock type support 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=20160512233935.GN3492@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=paul@pwsan.com \
    --cc=t-kristo@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).