[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a3c4c98a-45f6-4900-972d-379096e8244f@linaro.org>
Date: Fri, 25 Apr 2025 21:54:26 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Robert Foss <rfoss@...nel.org>, Todor Tomov <todor.too@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, loic.poulain@....qualcomm.com,
vladimir.zapolskiy@...aro.org, krzk@...nel.org,
linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] media: qcom: camss: x1e80100: Fixup x1e csiphy
supply names
On 25/04/2025 18:27, Dmitry Baryshkov wrote:
>> static const struct camss_subdev_resources csiphy_res_x1e80100[] = {
>> /* CSIPHY0 */
>> {
>> - .regulators = { "vdd-csiphy-0p8-supply",
>> - "vdd-csiphy-1p2-supply" },
>> + .regulators = { "vdd-csiphy0-0p8",
>> + "vdd-csiphy0-1p2" },
> This is an ABI break. Please mention in the cover message why we are
> allowing it.
Not an ABI break as we have no upstream consumer of this just yet.
I'll V3 this to make clear though.
---
bod
Powered by blists - more mailing lists