All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Neacsu <geocausa@gmail.com>
To: Bryan O'Donoghue <bod@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, David Heidelberg <david@ixit.cz>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Loic Poulain <loic.poulain@oss.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
	Vikram Sharma <vikram.sharma@oss.qualcomm.com>,
	Suresh Vankadara <svankada@qti.qualcomm.com>,
	tjose@qti.qualcomm.com,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-phy@lists.infradead.org, linux-media@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 0/4] phy: qcom-mipi-csi2: C-PHY for X1E80100
Date: Fri, 16 Oct 2026 12:32:59 +0100	[thread overview]
Message-ID: <20261016113259.40819-1-geocausa@gmail.com> (raw)
In-Reply-To: <b96649d9-5c1c-4fc0-a77d-d0076cf80b86@kernel.org>

Hi Bryan,

On 16/10/2026 12:02, Bryan O'Donoghue wrote:
> Small point of order here - this is not really @ RFC status.

Understood, v3 drops the RFC prefix.

>> The kernel was 7.1.5, with linux-next's CAMSS and CSI2 PHY built as
>> modules; the test build needed shims only for API differences.
>
> What's this ?
>
> "It builds" I can verify myself, "it works" is the thing. Just slow down
> and get something you can test on hardware.

Fair point. The frames in the cover letter were captured on the
hardware, but the kernel underneath was the 7.1.5 one this machine runs
day to day, with linux-next's CAMSS and CSI2 PHY sources built as modules
for it. That is not the same as running linux-next. Before v3 I will
boot an actual linux-next kernel on the Surface Pro 11, retest both
cameras there, and say exactly what was run.

For 4/4 I will also move the fsleep() change into its own patch with the
reasoning, and put the lanes_enable() decomposition in a precursor
patch, as you asked. Thanks for the reviews of 2/4 and 3/4.

Thanks,
George

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: George Neacsu <geocausa@gmail.com>
To: Bryan O'Donoghue <bod@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, David Heidelberg <david@ixit.cz>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Loic Poulain <loic.poulain@oss.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
	Vikram Sharma <vikram.sharma@oss.qualcomm.com>,
	Suresh Vankadara <svankada@qti.qualcomm.com>,
	tjose@qti.qualcomm.com,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-phy@lists.infradead.org, linux-media@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 0/4] phy: qcom-mipi-csi2: C-PHY for X1E80100
Date: Fri, 16 Oct 2026 12:32:59 +0100	[thread overview]
Message-ID: <20261016113259.40819-1-geocausa@gmail.com> (raw)
In-Reply-To: <b96649d9-5c1c-4fc0-a77d-d0076cf80b86@kernel.org>

Hi Bryan,

On 16/10/2026 12:02, Bryan O'Donoghue wrote:
> Small point of order here - this is not really @ RFC status.

Understood, v3 drops the RFC prefix.

>> The kernel was 7.1.5, with linux-next's CAMSS and CSI2 PHY built as
>> modules; the test build needed shims only for API differences.
>
> What's this ?
>
> "It builds" I can verify myself, "it works" is the thing. Just slow down
> and get something you can test on hardware.

Fair point. The frames in the cover letter were captured on the
hardware, but the kernel underneath was the 7.1.5 one this machine runs
day to day, with linux-next's CAMSS and CSI2 PHY sources built as modules
for it. That is not the same as running linux-next. Before v3 I will
boot an actual linux-next kernel on the Surface Pro 11, retest both
cameras there, and say exactly what was run.

For 4/4 I will also move the fsleep() change into its own patch with the
reasoning, and put the lanes_enable() decomposition in a precursor
patch, as you asked. Thanks for the reviews of 2/4 and 3/4.

Thanks,
George

  reply	other threads:[~2026-10-16 11:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <K9h_NQSPlrzzoVDIqqNPGT6KDZNScVi2mlqy6yNs8VOOS_I4KXf0QLy4k3Cwo2qKhnfL_qUK5wnY4h6wX24L4A==@protonmail.internalid>
2026-10-16 10:57 ` [PATCH RFC v2 0/4] phy: qcom-mipi-csi2: C-PHY for X1E80100 George Neacsu
2026-10-16 10:57   ` George Neacsu via B4 Relay
2026-10-16 10:57   ` George Neacsu via B4 Relay
2026-10-16 10:57   ` [PATCH RFC v2 1/4] phy: Add MIPI C-PHY mode and configuration options George Neacsu
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 11:04     ` sashiko-bot
2026-10-16 11:35     ` Nihal Kumar Gupta
2026-10-16 11:35       ` Nihal Kumar Gupta
2026-10-16 14:16     ` Loic Poulain
2026-10-16 14:16       ` Loic Poulain
2026-10-16 10:57   ` [PATCH RFC v2 2/4] phy: Add MIPI C-PHY configuration helpers George Neacsu
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 11:06     ` Bryan O'Donoghue
2026-10-16 11:06       ` Bryan O'Donoghue
2026-10-16 10:57   ` [PATCH RFC v2 3/4] phy: qcom-mipi-csi2: Rename the D-PHY init sequence George Neacsu
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 11:07     ` Bryan O'Donoghue
2026-10-16 11:07       ` Bryan O'Donoghue
2026-10-16 10:57   ` [PATCH RFC v2 4/4] phy: qcom-mipi-csi2: Add C-PHY support for X1E80100 George Neacsu
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 10:57     ` George Neacsu via B4 Relay
2026-10-16 11:15     ` Bryan O'Donoghue
2026-10-16 11:15       ` Bryan O'Donoghue
2026-10-16 11:35     ` Nihal Kumar Gupta
2026-10-16 11:35       ` Nihal Kumar Gupta
2026-10-16 12:05       ` Konrad Dybcio
2026-10-16 12:05         ` Konrad Dybcio
2026-10-16 12:25         ` Nihal Kumar Gupta
2026-10-16 12:25           ` Nihal Kumar Gupta
2026-10-16 12:24     ` David Heidelberg
2026-10-16 12:24       ` David Heidelberg
2026-10-16 11:02   ` [PATCH RFC v2 0/4] phy: qcom-mipi-csi2: C-PHY " Bryan O'Donoghue
2026-10-16 11:02     ` Bryan O'Donoghue
2026-10-16 11:32     ` George Neacsu [this message]
2026-10-16 11:32       ` George Neacsu
2026-10-16 13:27       ` Bryan O'Donoghue
2026-10-16 13:27         ` Bryan O'Donoghue
2026-10-16 14:55         ` George Neacsu
2026-10-16 14:55           ` George Neacsu

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=20261016113259.40819-1-geocausa@gmail.com \
    --to=geocausa@gmail.com \
    --cc=bod@kernel.org \
    --cc=david@ixit.cz \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --cc=mani@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=nihal.gupta@oss.qualcomm.com \
    --cc=svankada@qti.qualcomm.com \
    --cc=tjose@qti.qualcomm.com \
    --cc=vikram.sharma@oss.qualcomm.com \
    --cc=vkoul@kernel.org \
    --cc=vladimir.zapolskiy@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.