From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Prajval Chaudhary <prajvalchaudhari733@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v4 1/2] staging: media: atomisp: Remove pad_w and pad_h module parameters
Date: Sun, 4 Oct 2026 00:27:55 +0300 [thread overview]
Message-ID: <asFzWx6BOBbs5meb@kekkonen.localdomain> (raw)
In-Reply-To: <20260721163533.15888-2-prajvalchaudhari733@gmail.com>
Hi Prajval,
On Tue, Jul 21, 2026 at 10:05:31PM +0530, Prajval Chaudhary wrote:
> Remove the 'pad_w' and 'pad_h' module parameters to prevent userspace
> from overriding internal ISP hardware padding boundaries. Convert them
> into internal driver constants instead.
>
> Signed-off-by: Prajval Chaudhary <prajvalchaudhari733@gmail.com>
> ---
> drivers/staging/media/atomisp/pci/atomisp_common.h | 4 ++--
> drivers/staging/media/atomisp/pci/atomisp_v4l2.c | 8 ++------
> 2 files changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/atomisp_common.h b/drivers/staging/media/atomisp/pci/atomisp_common.h
> index a2462fc306fb..7c6c0124ff72 100644
> --- a/drivers/staging/media/atomisp/pci/atomisp_common.h
> +++ b/drivers/staging/media/atomisp/pci/atomisp_common.h
> @@ -22,8 +22,8 @@
>
> extern int dbg_level;
> extern int dbg_func;
> -extern int pad_w;
> -extern int pad_h;
> +extern const int pad_w;
> +extern const int pad_h;
Please switch to macros while at it, with an appropriate prefix, e.g.
ATOMISP_PAD_[WH].
>
> /* Minimum padding requirements for ISP2400 (BYT) */
> #define ISP2400_MIN_PAD_W 12
> diff --git a/drivers/staging/media/atomisp/pci/atomisp_v4l2.c b/drivers/staging/media/atomisp/pci/atomisp_v4l2.c
> index 812230397409..d117fea2860c 100644
> --- a/drivers/staging/media/atomisp/pci/atomisp_v4l2.c
> +++ b/drivers/staging/media/atomisp/pci/atomisp_v4l2.c
> @@ -64,13 +64,9 @@ MODULE_PARM_DESC(dbg_func,
> * output res, and isp output res. however since we do not have this yet,
> * the chosen solution is the next best thing.
> */
> -int pad_w = 16;
> -module_param(pad_w, int, 0644);
> -MODULE_PARM_DESC(pad_w, "extra data for ISP processing");
> +const int pad_w = 16;
>
> -int pad_h = 16;
> -module_param(pad_h, int, 0644);
> -MODULE_PARM_DESC(pad_h, "extra data for ISP processing");
> +const int pad_h = 16;
>
> /*
> * FIXME: this is a hack to make easier to support ISP2401 variant.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-10-03 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 16:35 [PATCH v4 0/2] staging: media: atomisp: Cleanup unused " Prajval Chaudhary
2026-07-21 16:35 ` [PATCH v4 1/2] staging: media: atomisp: Remove pad_w and pad_h " Prajval Chaudhary
2026-10-03 21:27 ` Sakari Ailus [this message]
2026-07-21 16:35 ` [PATCH v4 2/2] staging: media: atomisp: Remove dbg_level and dbg_func " Prajval Chaudhary
2026-07-21 20:55 ` Andy Shevchenko
2026-10-03 21:30 ` Sakari Ailus
2026-07-21 20:56 ` [PATCH v4 0/2] staging: media: atomisp: Cleanup unused " Andy Shevchenko
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=asFzWx6BOBbs5meb@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=prajvalchaudhari733@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
all inboxes | Powered by JetHome®