[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <154835777525.136743.6424256006615217720@swboyd.mtv.corp.google.com>
Date: Thu, 24 Jan 2019 11:22:55 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Andy Gross <andy.gross@...aro.org>,
AngeloGioacchino Del Regno <kholk11@...il.com>,
David Brown <david.brown@...aro.org>,
Michael Turquette <mturquette@...libre.com>
Cc: AngeloGioacchino Del Regno <kholk11@...il.com>,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-soc@...r.kernel.org
Subject: Re: [PATCH] clk: qcom: Add MSM8976/56 Global Clock Controller (GCC) driver
Quoting AngeloGioacchino Del Regno (2019-01-12 07:03:18)
> From 50465f2a4454625aac622bb84dbecdeaf5a50904 Mon Sep 17 00:00:00 2001
> From: "Angelo G. Del Regno" <kholk11@...il.com>
> Date: Sat, 12 Jan 2019 10:52:18 +0100
> Subject: [PATCH] clk: qcom: Add MSM8976/56 Global Clock Controller (GCC)
> driver
>
> Add support for the global clock controller found on MSM8976
> and MSM8976 SoCs.
> Since the multimedia clocks are actually in the GCC on these
> SoCs, this will allow drivers to probe and control basically
> all the required clocks.
>
> Signed-off-by: Angelo G. Del Regno <kholk11@...il.com>
Are you going to send out DTS bits and provide platform support? I'm not
interested in merging the clk bits and then having to support a driver
that never gets used.
Also, is this copy/pasted from some downstream kernel sources? Would be
good to have a pointer to that so we can compare and see if you've
changed anything.
Powered by blists - more mailing lists