From: Tero Kristo <t-kristo@ti.com>
To: <santosh.shilimkar@oracle.com>, <linux-clk@vger.kernel.org>,
<sboyd@kernel.org>, <mturquette@baylibre.com>,
<ssantosh@kernel.org>, <nm@ti.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv2 0/5] clk: keystone: clock optimizations / fixes
Date: Wed, 5 Jun 2019 10:50:57 +0300 [thread overview]
Message-ID: <a0f19a9a-e06a-324b-82fe-ec0024f56fe0@ti.com> (raw)
In-Reply-To: <7d97db9a-71fd-0c44-a4ef-ef4d726cdb20@oracle.com>
On 04/06/2019 20:55, santosh.shilimkar@oracle.com wrote:
> On 5/28/19 6:10 AM, Tero Kristo wrote:
>> Hi,
>>
>> This is a re-base / re-spin of the Keystone clock optimization series
>> [1].
>>
>> Changes from v1:
>> - rebased on top of 5.2-rc1
>> - added support for clk-ids 255+
>> - changed patch #3 to parse also 'assigned-clocks' in addition to
>> 'clocks'
>> DT nodes only. This allows automatic (DT based) programming of clocks
>> that are not directly touched by any driver.
>>
>> Please note that there is hard dependency between patches 4 & 5, patch #5
>> must be applied after patch #4, otherwise bad things will happen
>> (basically
>> boot breaks.) The cast magic in patch #4 is done also so that this order
>> of patches can be used and bisectability is retained.
>>
> Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
Thanks Santosh,
Stephen, are you going to be picking these up directly or do you want me
to send a pull-req?
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
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:[~2019-06-05 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 13:10 [PATCHv2 0/5] clk: keystone: clock optimizations / fixes Tero Kristo
2019-05-28 13:10 ` [PATCHv2 1/5] clk: keystone: sci-clk: cut down the clock name length Tero Kristo
2019-05-28 13:10 ` [PATCHv2 2/5] clk: keystone: sci-clk: split out the fw clock parsing to own function Tero Kristo
2019-05-28 13:10 ` [PATCHv2 3/5] clk: keystone: sci-clk: probe clocks from DT instead of firmware Tero Kristo
2019-05-28 13:10 ` [PATCHv2 4/5] clk: keystone: sci-clk: extend clock IDs to 32 bits Tero Kristo
2019-05-28 13:10 ` [PATCHv2 5/5] firmware: ti_sci: extend clock identifiers from u8 to u32 Tero Kristo
2019-06-04 17:55 ` [PATCHv2 0/5] clk: keystone: clock optimizations / fixes santosh.shilimkar
2019-06-05 7:50 ` Tero Kristo [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=a0f19a9a-e06a-324b-82fe-ec0024f56fe0@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sboyd@kernel.org \
--cc=ssantosh@kernel.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;
as well as URLs for NNTP newsgroup(s).