[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e781c2d21e346cdd7f84c3b7a57dafc.sboyd@kernel.org>
Date: Tue, 22 Aug 2023 12:10:25 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Jie Luo <quic_luoj@...cinc.com>,
Konrad Dybcio <konrad.dybcio@...aro.org>, agross@...nel.org,
andersson@...nel.org, catalin.marinas@....com, conor+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, mturquette@...libre.com,
p.zabel@...gutronix.de, robh+dt@...nel.org, will@...nel.org
Cc: linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
quic_srichara@...cinc.com
Subject: Re: [PATCH v3 3/3] clk: qcom: add clock controller driver for qca8386/qca8084
Quoting Jie Luo (2023-08-14 03:58:26)
>
>
> On 8/12/2023 6:56 PM, Konrad Dybcio wrote:
> > My main point is, why can't you use qcom_cc_really_probe?
> >
>
> Hi Konrad,
> qcom_cc_really_probe is taking the platform_device as the input
> parameter, but the nss_cc_qca8k_probe takes the mdio_device as the probe
> parameter.
There's no real reason why it takes a platform device instead of a plain
struct device. You can have an earlier patch change that function to
take a struct device instead.
Powered by blists - more mailing lists