linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Knecht <vincent.knecht@mailoo.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	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>,
	Bjorn Andersson	 <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	"André Apitzsch" <git@apitzsch.eu>,
	phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 2/4] media: qcom: camss: Add support for MSM8939
Date: Mon, 26 May 2025 18:28:30 +0200	[thread overview]
Message-ID: <a1645a74b59c29a567477e4b3a42391f40ba0591.camel@mailoo.org> (raw)
In-Reply-To: <cc43d9b7-13ba-44ea-9b37-fc54c0d1f2e0@linaro.org>

Le lundi 26 mai 2025 à 09:20 +0100, Bryan O'Donoghue a écrit :
> On 25/05/2025 20:25, Vincent Knecht via B4 Relay wrote:
> > From: Vincent Knecht <vincent.knecht@mailoo.org>
> > 
> > The camera subsystem for the MSM8939 is the same as MSM8916 except with
> > 3 CSID instead of 2, and some higher clock rates.
> > 
> > As a quirk, this SoC needs writing values to 2 VFE VBIF registers
> > (see downstream msm8939-camera.dtsi vbif-{regs,settings} properties).
> > This fixes black stripes across sensor and garbage in CSID TPG outputs.
> > 
> > Add support for the MSM8939 camera subsystem.
> > 
> > Signed-off-by: Vincent Knecht <vincent.knecht@mailoo.org>
> > ---
> >   drivers/media/platform/qcom/camss/camss-csiphy.c   |   1 +
> >   drivers/media/platform/qcom/camss/camss-ispif.c    |   8 +-
> >   drivers/media/platform/qcom/camss/camss-vfe-vbif.c |   7 +
> >   drivers/media/platform/qcom/camss/camss-vfe.c      |   1 +
> >   drivers/media/platform/qcom/camss/camss.c          | 157 +++++++++++++++++++++
> >   drivers/media/platform/qcom/camss/camss.h          |   1 +
> >   6 files changed, 173 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/media/platform/qcom/camss/camss-csiphy.c b/drivers/media/platform/qcom/camss/camss-csiphy.c
> > index c622efcc92ff3781d7fc3ace0253c2d64c91e847..6311fc2975aa1345e430a477c8a6476f1d7e5663 100644
> > --- a/drivers/media/platform/qcom/camss/camss-csiphy.c
> > +++ b/drivers/media/platform/qcom/camss/camss-csiphy.c
> > @@ -605,6 +605,7 @@ int msm_csiphy_subdev_init(struct camss *camss,
> >   		return PTR_ERR(csiphy->base);
> >   
> >   	if (camss->res->version == CAMSS_8x16 ||
> > +	    camss->res->version == CAMSS_8x39 ||
> >   	    camss->res->version == CAMSS_8x53 ||
> >   	    camss->res->version == CAMSS_8x96) {
> >   		csiphy->base_clk_mux =
> > diff --git a/drivers/media/platform/qcom/camss/camss-ispif.c b/drivers/media/platform/qcom/camss/camss-ispif.c
> > index 2dc585c6123dd248a5bacd9c7a88cb5375644311..aaf3caa42d33dcb641651e7f5bc0c2a564d85bfa 100644
> > --- a/drivers/media/platform/qcom/camss/camss-ispif.c
> > +++ b/drivers/media/platform/qcom/camss/camss-ispif.c
> > @@ -1112,6 +1112,8 @@ int msm_ispif_subdev_init(struct camss *camss,
> >   	/* Number of ISPIF lines - same as number of CSID hardware modules */
> >   	if (camss->res->version == CAMSS_8x16)
> >   		ispif->line_num = 2;
> > +	else if (camss->res->version == CAMSS_8x39)
> > +		ispif->line_num = 3;
> 
> > +		.interrupt = { "vfe0" },
> > +		.vfe = {
> > +			.line_num = 3,
> 
> Hmm should we really be setting line_num inline in the code ?
> 
> I don't believe we should.
> 
> These parameters should be passed from the resources structures.
> 
> ---
> bod

I've just followed suit, no strong opinion about it.
Can we agree this could be changed in another series ?



  reply	other threads:[~2025-05-26 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 19:25 [PATCH v2 0/4] CAMSS support for MSM8939 Vincent Knecht via B4 Relay
2025-05-25 19:25 ` [PATCH v2 1/4] media: qcom: camss: vfe: Add VBIF setting support Vincent Knecht via B4 Relay
2025-05-26  8:08   ` Bryan O'Donoghue
     [not found]     ` <10c45ae1d2453f7c81dadeb132b6c2911ab7d95c.camel@mailoo.org>
2025-05-27  8:19       ` Bryan O'Donoghue
2025-05-26  8:13   ` Bryan O'Donoghue
2025-05-26 16:23     ` Vincent Knecht
2025-05-27 12:01       ` Bryan O'Donoghue
2025-05-25 19:25 ` [PATCH v2 2/4] media: qcom: camss: Add support for MSM8939 Vincent Knecht via B4 Relay
2025-05-26  8:20   ` Bryan O'Donoghue
2025-05-26 16:28     ` Vincent Knecht [this message]
2025-05-25 19:25 ` [PATCH v2 3/4] media: dt-bindings: Add qcom,msm8939-camss Vincent Knecht via B4 Relay
2025-05-25 19:25 ` [PATCH v2 4/4] arm64: dts: qcom: msm8939: Add camss and cci Vincent Knecht via B4 Relay
2025-05-27 11:57 ` [PATCH v2 0/4] CAMSS support for MSM8939 Konrad Dybcio

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=a1645a74b59c29a567477e4b3a42391f40ba0591.camel@mailoo.org \
    --to=vincent.knecht@mailoo.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@apitzsch.eu \
    --cc=konradybcio@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=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;
as well as URLs for NNTP newsgroup(s).