From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Marshall <pm@petermarshall.ca>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
Sylvain Petinot <sylvain.petinot@foss.st.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/7] media: i2c: vd55g: move patch array to a separate firmware header
Date: Thu, 3 Sep 2026 15:37:33 +0200 [thread overview]
Message-ID: <20260903-determined-tough-toad-ad3fb8@quoll> (raw)
In-Reply-To: <20260902204549.657228-2-pm@petermarshall.ca>
On Wed, Sep 02, 2026 at 04:45:40PM -0400, Peter Marshall wrote:
> A firmware patch consisting of an array of bytes is uploaded to the chip
> during its boot sequence. Declutter the driver source by moving it to a
> separate header file.
>
> Signed-off-by: Peter Marshall <pm@petermarshall.ca>
> ---
> drivers/media/i2c/vd55g-fw.h | 305 +++++++++++++++++++++++++++++++++++
> drivers/media/i2c/vd55g1.c | 296 +--------------------------------
> 2 files changed, 306 insertions(+), 295 deletions(-)
> create mode 100644 drivers/media/i2c/vd55g-fw.h
>
> diff --git a/drivers/media/i2c/vd55g-fw.h b/drivers/media/i2c/vd55g-fw.h
> new file mode 100644
> index 000000000..02faed7e4
> --- /dev/null
> +++ b/drivers/media/i2c/vd55g-fw.h
> @@ -0,0 +1,305 @@
> +/* SPDX-License-Identifier: GPL-2.0
> + *
> + * Driver for VD55G1 global shutter sensor family driver
> + *
> + * Copyright (C) 2025 STMicroelectronics SA
> + */
> +
> +#include <linux/kernel.h>
> +#include <linux/types.h>
> +
> +static const u8 vd55g1_patch_array[] = {
Headers should have data, because this can easily lead to duplicated
objects.
static arrays go to C units.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-03 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 20:45 [PATCH 0/7] media: i2c: st-vd55g1: Genericize driver and add VD55G0 support Peter Marshall
2026-09-02 20:45 ` [PATCH 1/7] media: i2c: vd55g: move patch array to a separate firmware header Peter Marshall
2026-09-03 13:37 ` Krzysztof Kozlowski [this message]
2026-09-02 20:45 ` [PATCH 2/7] dt-bindings: media: i2c: st,vd55g: rename and add VD55G0 variant Peter Marshall
2026-09-03 13:36 ` Krzysztof Kozlowski
2026-09-02 20:45 ` [PATCH 3/7] media: ipu-bridge: Add VD55G0 to the list of supported sensors Peter Marshall
2026-09-02 20:45 ` [PATCH 4/7] platform/x86: int3472: Add VD55G0 supply GPIO mapping Peter Marshall
2026-09-02 20:45 ` [PATCH 5/7] media: i2c: st-vd55g: Add generic driver and VD55G0 support Peter Marshall
2026-09-03 13:41 ` Krzysztof Kozlowski
2026-09-02 20:45 ` [PATCH 6/7] media: i2c: st-vd55g: Remove legacy vd55g1 remnants Peter Marshall
2026-09-03 13:43 ` Krzysztof Kozlowski
2026-09-02 20:45 ` [PATCH 7/7] MAINTAINERS: Update ST VD55G camera driver entry Peter Marshall
2026-09-03 13:43 ` Krzysztof Kozlowski
2026-09-04 12:06 ` [PATCH 0/7] media: i2c: st-vd55g1: Genericize driver and add VD55G0 support Benjamin Mugnier
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=20260903-determined-tough-toad-ad3fb8@quoll \
--to=krzk@kernel.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pm@petermarshall.ca \
--cc=sakari.ailus@linux.intel.com \
--cc=sylvain.petinot@foss.st.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®