[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3370cff3-9296-74fc-8e7d-ff93c3978351@marek.ca>
Date: Wed, 23 Sep 2020 12:24:04 -0400
From: Jonathan Marek <jonathan@...ek.ca>
To: Stephen Boyd <sboyd@...nel.org>, 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
On 9/22/20 3:04 PM, Stephen Boyd wrote:
> 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?
>
Possibly, the biggest difference seems to be the plls (trion vs lucid,
different config), which could be resolved in the probe() function. If
you think combining the drivers is the right thing to do then I can do that.
Powered by blists - more mailing lists