Linux Kernel Mentees list
 help / color / mirror / Atom feed
From: Jai Luthra <jai.luthra@ideasonboard.com>
To: Tharit Tangkijwanichakul <tharitt97@gmail.com>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] media: imx219: fix test pattern ordering and add patterns
Date: Wed, 01 Jul 2026 12:23:10 +0530	[thread overview]
Message-ID: <178288879026.1799417.14880182647984884282@freya> (raw)
In-Reply-To: <CACak8wPuBaGCBbBrpoPQ5ftQRtqwijvN_VJoRGs7FzYBGck-iA@mail.gmail.com>

Hi Tharit,

Quoting Tharit Tangkijwanichakul (2026-06-26 18:08:20)
> Hi Jai,
> 
> Thanks for the review
> 
> > Do you have a strong reason to switch this to the datasheet values?
> 
> I must say there is no strong reason. I'm totally new here and come from
> the perspective of someone studying how to write a camera sensor driver.
> The datasheet says that writing 0x1 to reg 0x0601 will set the mode to solid
> color test pattern. So it is "natural" to expect that I should set
> test_pattern=1 to do so via v4l2-ctl.
> 
> > I ask because this might break what userspace applications expect
> > (libcamera) and also automated capture tests (that compare md5sums of the
> > test pattern) in vendor board-farms.
> 
> This was totally oblivious to me when I made the change.
> I agree with you on this point. Breaking userspace does not sound like
> a good idea.
> 
> I'm open to making a v3 patch and only introduce new test patterns to
> the driver.
> 

Yes please do so.

Thanks,
    Jai

> Best,
> Tharit

  reply	other threads:[~2026-07-01  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 16:02 [PATCH] media: imx219: fix test pattern ordering and add patterns Tharit Tangkijwanichakul
2026-06-26 10:04 ` Jai Luthra
2026-06-26 12:38   ` Tharit Tangkijwanichakul
2026-07-01  6:53     ` Jai Luthra [this message]
2026-07-01 12:59       ` Tharit Tangkijwanichakul

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=178288879026.1799417.14880182647984884282@freya \
    --to=jai.luthra@ideasonboard.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=skhan@linuxfoundation.org \
    --cc=tharitt97@gmail.com \
    /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