[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <160080149549.310579.17453759593211612997@swboyd.mtv.corp.google.com>
Date: Tue, 22 Sep 2020 12:04:55 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Jonathan Marek <jonathan@...ek.ca>, linux-arm-msm@...r.kernel.org
Cc: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH v3 6/7] clk: qcom: Add display clock controller driver for SM8150
Quoting Jonathan Marek (2020-09-11 08:34:06)
> Add support for the display clock controller found on SM8150
> based devices. This would allow display drivers to probe and
> control their clocks.
>
> Signed-off-by: Jonathan Marek <jonathan@...ek.ca>
> ---
> drivers/clk/qcom/Kconfig | 9 +
> drivers/clk/qcom/Makefile | 1 +
> drivers/clk/qcom/dispcc-sm8150.c | 1152 ++++++++++++++++++++++++++++++
> 3 files changed, 1162 insertions(+)
> create mode 100644 drivers/clk/qcom/dispcc-sm8150.c
If the bindings are the same for these two drivers I wonder if there is
anything different between the two. Maybe the two drivers can be one
driver?
Powered by blists - more mailing lists