[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <572826F4.3080500@ti.com>
Date: Tue, 3 May 2016 09:50:04 +0530
From: Lokesh Vutla <lokeshvutla@...com>
To: "J.D. Schroeder" <Linux.HWI@...min.com>,
<linux-kernel@...r.kernel.org>, <t-kristo@...com>,
<bcousson@...libre.com>, <tony@...mide.com>, <robh+dt@...nel.org>,
<pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<linux@....linux.org.uk>, <linux-omap@...r.kernel.org>,
<devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
CC: <jay.schroeder@...min.com>
Subject: Re: [PATCH v2 0/3] AM57/DRA7 Clock Tree DTSI Fix-ups
On Monday 02 May 2016 10:42 PM, J.D. Schroeder wrote:
> This series of patches fixes several discrepancies between the
> AM57/DRA7 clock tree description and the actual hardware behavior and
> frequencies. With these changes a more complete picture of the clock
> tree is represented for a few of the clocks and their resulting
> frequencies.
Tested on my DRA74-evm.
Tested-by: Lokesh Vutla <lokeshvutla@...com>
Thanks and regards,
Lokesh
>
> v2 Changes:
> * Rebased on linux-next as requested by Tony Lindgren
> * Eliminated previous patch 2 as another change fixing the same thing
> was merged in eea08802f586acd6aef377d1b4a541821013cc0b
> * Added to the commit message in patch 2 to clarify the source of the
> clock being internal to the processor
> * Added a new patch 3 to fix a new warning introduced by
> eea08802f586acd6aef377d1b4a541821013cc0b
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Powered by blists - more mailing lists