From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Luca Weiss <luca.weiss@fairphone.com>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Barnabas Czeman <barnabas.czeman@mainlining.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Caleb Connolly <caleb.connolly@linaro.org>,
David Heidelberg <david@ixit.cz>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] media: qcom: camss: Restrict endpoint bus-type to D-PHY
Date: Fri, 13 Dec 2024 13:02:59 +0200 [thread overview]
Message-ID: <a047e4b8-c2d6-4486-8037-e7b854660cb1@linaro.org> (raw)
In-Reply-To: <9c89e6f4-a9af-4270-b266-537f3464ee32@linaro.org>
On 12/9/24 14:32, Bryan O'Donoghue wrote:
> On 09/12/2024 12:01, Luca Weiss wrote:
>> Currently the Qualcomm CAMSS driver only supports D-PHY while the
>> hardware on most SoCs also supports C-PHY. Until this support is added,
>> check for D-PHY to make it somewhat explicit that C-PHY won't work.
>>
>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>> ---
>> drivers/media/platform/qcom/camss/camss.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/media/platform/qcom/camss/camss.c b/drivers/media/platform/qcom/camss/camss.c
>> index 9fb31f4c18adee886cd0bcf84438a8f27635e07f..b99af35074cdf6fa794a0d2f0d54ecf12ac354d9 100644
>> --- a/drivers/media/platform/qcom/camss/camss.c
>> +++ b/drivers/media/platform/qcom/camss/camss.c
>> @@ -1855,6 +1855,15 @@ static int camss_of_parse_endpoint_node(struct device *dev,
>> if (ret)
>> return ret;
>>
>> + /*
>> + * Most SoCs support both D-PHY and C-PHY standards, but currently only
>> + * D-PHY is supported in the driver.
>> + */
>> + if (vep.bus_type != V4L2_MBUS_CSI2_DPHY) {
>> + dev_err(dev, "Unsupported bus type %d\n", vep.bus_type);
>> + return -EINVAL;
>> + }
>> +
Looks like it would break all old board dtbs, which is not just bad, but NAK.
V4L2_MBUS_UNKNOWN shall be properly handled without the risk of regressions.
>> csd->interface.csiphy_id = vep.base.port;
>>
>> mipi_csi2 = &vep.bus.mipi_csi2;
>>
>
> Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2024-12-13 11:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 12:01 [PATCH 0/2] Some small preparations around CAMSS D-PHY / C-PHY support Luca Weiss
2024-12-09 12:01 ` [PATCH 1/2] media: dt-bindings: media: camss: Restrict bus-type property Luca Weiss
2024-12-09 12:31 ` Bryan O'Donoghue
2024-12-13 9:34 ` Krzysztof Kozlowski
2024-12-13 9:39 ` Luca Weiss
2024-12-13 10:50 ` Vladimir Zapolskiy
2024-12-13 11:24 ` Luca Weiss
2024-12-13 11:34 ` Bryan O'Donoghue
2024-12-13 11:54 ` Vladimir Zapolskiy
2024-12-13 12:09 ` Bryan O'Donoghue
2024-12-09 12:01 ` [PATCH 2/2] media: qcom: camss: Restrict endpoint bus-type to D-PHY Luca Weiss
2024-12-09 12:32 ` Bryan O'Donoghue
2024-12-13 11:02 ` Vladimir Zapolskiy [this message]
2024-12-13 11:22 ` Luca Weiss
2024-12-13 11:49 ` Vladimir Zapolskiy
2024-12-13 17:58 ` Vladimir Zapolskiy
[not found] ` <6756eb28.050a0220.34a8dd.2e9b@mx.google.com>
2024-12-09 13:08 ` [0/2] Some small preparations around CAMSS D-PHY / C-PHY support Luca Weiss
2025-02-26 14:13 ` [PATCH 0/2] " Luca Weiss
2025-02-26 14:47 ` Bryan O'Donoghue
2025-03-17 7:45 ` Luca Weiss
2025-04-07 10:01 ` Bryan O'Donoghue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a047e4b8-c2d6-4486-8037-e7b854660cb1@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=barnabas.czeman@mainlining.org \
--cc=bryan.odonoghue@linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox