[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ff128062-5c1f-4abe-8582-543063d5e526@linaro.org>
Date: Thu, 1 Aug 2024 11:59:38 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Depeng Shao <quic_depengs@...cinc.com>,
Krzysztof Kozlowski <krzk@...nel.org>, rfoss@...nel.org,
todor.too@...il.com, mchehab@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org
Cc: quic_eberman@...cinc.com, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel@...cinc.com,
Yongsheng Li <quic_yon@...cinc.com>
Subject: Re: [PATCH 09/13] media: qcom: camss: Add CSID Gen3 support for
SM8550
On 01/08/2024 02:53, Depeng Shao wrote:
> but the issue is that the sm8550 can be probed once having patch set 1,
> but the sm8550_resources isn't complete in patch set 1.
Doesn't matter until you _upstream_ a dts that operates on it.
Its not a massive deal if you start at patch #1 and and patch #1+n and a
there are a few warnings in between as you add stuff in but, for
preference every single patch applies and builds warning free.
If you
- Add bindings
- Do driver stuff
- Then do dts stuff
You don't need to worry about probe() doing mad things.
---
bod
Powered by blists - more mailing lists