public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: 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 0/2] Some small preparations around CAMSS D-PHY / C-PHY support
Date: Wed, 26 Feb 2025 14:47:01 +0000	[thread overview]
Message-ID: <eb06daf1-3cc3-4b31-a0bf-bc450cd0f041@linaro.org> (raw)
In-Reply-To: <D82FU3SIX5RZ.1Y525GJO0UOAA@fairphone.com>

On 26/02/2025 14:13, Luca Weiss wrote:
> Hi all,
> 
> On Mon Dec 9, 2024 at 1:01 PM CET, Luca Weiss wrote:
>> Since the hardware blocks on the SoCs generally support both D-PHY and
>> C-PHY standards for camera, but the camss driver currently is only
>> supporting D-PHY, do some preparations in order to add C-PHY support at
>> some point.
>>
>> Make the dt bindings explicit that the hardware supports both (except
>> for MSM8916) but also add a check to the driver that errors out in case
>> a dt tries to use C-PHY since that's not supported yet.
>>
>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>> ---
>> Luca Weiss (2):
>>        media: dt-bindings: media: camss: Restrict bus-type property
>>        media: qcom: camss: Restrict endpoint bus-type to D-PHY
> 
> This series is still pending, both patches got reviews and no pending
> comments from what I can see.
> 
> Would be nice to get it in for 6.15.
> 
Yes this should be merged.

Thanks for following up.

---
bod

  reply	other threads:[~2025-02-26 14:47 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
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 [this message]
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=eb06daf1-3cc3-4b31-a0bf-bc450cd0f041@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=barnabas.czeman@mainlining.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