From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: mchehab@kernel.org, sakari.ailus@linux.intel.com,
shravan kumar <shravan.chippa@microchip.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
conor.dooley@microchip.com,
valentina.fernandezalanis@microchip.com,
praveen.kumar@microchip.com, shravan.chippa@microchip.com
Subject: Re: [PATCH] media: i2c: imx334: add support for additional test patterns
Date: Tue, 24 Jun 2025 10:57:44 +0100 [thread overview]
Message-ID: <175075906452.3871677.12511426007175753529@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <20250624065438.2021044-1-shravan.chippa@microchip.com>
Hi Shravan
Quoting shravan kumar (2025-06-24 07:54:38)
> From: Shravan Chippa <shravan.chippa@microchip.com>
>
> Added support for three additional test patterns in the
> IMX334 driver: Black and Grey Bars, Black Color, and White Color.
>
> Signed-off-by: Shravan Chippa <shravan.chippa@microchip.com>
> ---
> drivers/media/i2c/imx334.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
> index 846b9928d4e8..43dd7edb48c8 100644
> --- a/drivers/media/i2c/imx334.c
> +++ b/drivers/media/i2c/imx334.c
> @@ -118,6 +118,9 @@
> #define IMX334_REG_TP CCI_REG8(0x329e)
> #define IMX334_TP_COLOR_HBARS 0xa
> #define IMX334_TP_COLOR_VBARS 0xb
> +#define IMX334_TP_BLACK 0x0
> +#define IMX334_TP_WHITE 0x1
> +#define IMX334_TP_BLACK_GREY 0xC
This should be lower case to match the other hex constants (0xc)
I also wonder if this list should be in register address order ... but
then it won't match the menu items ...
>
> #define IMX334_TPG_EN_DOUT CCI_REG8(0x329c)
> #define IMX334_TP_ENABLE 0x1
> @@ -398,12 +401,18 @@ static const char * const imx334_test_pattern_menu[] = {
> "Disabled",
> "Vertical Color Bars",
> "Horizontal Color Bars",
> + "Black and Grey Bars",
> + "Black Color",
> + "White Color",
> };
>
> static const int imx334_test_pattern_val[] = {
> IMX334_TP_DISABLE,
> IMX334_TP_COLOR_HBARS,
> IMX334_TP_COLOR_VBARS,
> + IMX334_TP_BLACK_GREY,
> + IMX334_TP_BLACK,
> + IMX334_TP_WHITE,
> };
>
> static const struct cci_reg_sequence raw10_framefmt_regs[] = {
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-06-24 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 6:54 shravan kumar
2025-06-24 9:57 ` Kieran Bingham [this message]
2025-06-26 7:09 ` Shravan.Chippa
2025-06-29 10:20 ` Sakari Ailus
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=175075906452.3871677.12511426007175753529@ping.linuxembedded.co.uk \
--to=kieran.bingham@ideasonboard.com \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=praveen.kumar@microchip.com \
--cc=sakari.ailus@linux.intel.com \
--cc=shravan.chippa@microchip.com \
--cc=valentina.fernandezalanis@microchip.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
all inboxes | Powered by JetHome®