[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4beb98e-df9e-43a9-9a4b-85962214274d@linaro.org>
Date: Sat, 30 Sep 2023 16:15:50 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
andersson@...nel.org, agross@...nel.org, konrad.dybcio@...aro.org,
mturquette@...libre.com, sboyd@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
jonathan@...ek.ca, quic_tdas@...cinc.com,
vladimir.zapolskiy@...aro.org
Cc: linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/5] dt-bindings: clock: Add SM8550 CAMCC yaml
On 30/09/2023 15:41, Bryan O'Donoghue wrote:
> The SM8550 should have its own yaml description file, not be listed as a
> compatible string of the SM8450 CAMCC driver since SM8450 and SM8550
> have separate CAMCC drivers.
Linux driver architecture does not shape bindings. If devices are
similar, it does not matter that you have two drivers. It was never a
valid reason to split bindings.
Best regards,
Krzysztof
Powered by blists - more mailing lists