public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: t-kristo@ti•com (Tero Kristo)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 1/3] clk: ti: am335x/am4372: Add tbclk to pwm node
Date: Mon, 21 Mar 2016 21:34:23 +0200	[thread overview]
Message-ID: <56F04CBF.7080506@ti.com> (raw)
In-Reply-To: <20160321184318.GS25972@codeaurora.org>

On 03/21/2016 08:43 PM, Stephen Boyd wrote:
> On 03/17, Franklin S Cooper Jr wrote:
>> Add tblck to the pwm nodes. This insures that the ehrpwm driver has access
>> to the time-based clk.
>>
>> Do not remove similar entries for ehrpwm node. Later patches will switch
>> from using ehrpwm node name to pwm. But to maintain ABI compatibility we
>> shouldn't remove the old entries.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti•com>
>> ---
>
> Acked-by: Stephen Boyd <sboyd@codeaurora•org>
>
> Are there any plans to get off these DT_CLK entries entirely?

The series that adds support for the hwmod clock type for OMAPs has a 
support patch that should address this problem at least partially; I am 
planning to post next rev of that set soonish. It should allow getting 
rid of majority of the clock aliases, I will remove any aliases I can at 
the same time.

-Tero

  reply	other threads:[~2016-03-21 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  1:15 [PATCH v3 0/3] ARM: am335x/am437x: Correct PWM bindings Franklin S Cooper Jr
2016-03-18  1:15 ` [PATCH v3 1/3] clk: ti: am335x/am4372: Add tbclk to pwm node Franklin S Cooper Jr
2016-03-21 18:43   ` Stephen Boyd
2016-03-21 19:34     ` Tero Kristo [this message]
2016-03-18  1:15 ` [PATCH v3 2/3] ARM: DTS: da850/am4372/am33xx: Use generic node name for ehrpwm Franklin S Cooper Jr
2016-04-12 21:07   ` Tony Lindgren
2016-03-18  1:15 ` [PATCH v3 3/3] pwm: pwm-tiehrpwm: Update dt binding document to use generic node name Franklin S Cooper Jr
2016-03-20  0:40   ` Rob Herring
2016-06-10 12:37   ` Thierry Reding

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=56F04CBF.7080506@ti.com \
    --to=t-kristo@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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