From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: laurent.pinchart@ideasonboard.com, martin.hecht@avnet.eu,
michael.roeder@avnet.eu, linuxfancy@googlegroups.com,
mhecht73@gmail.com, christophe.jaillet@wanadoo.fr,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Gerald Loacker <gerald.loacker@wolfvision.net>,
Nicholas Roth <nicholas@rothemail.net>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Daniel Scally <djrscally@gmail.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v14 3/3] media: i2c: Add support for alvium camera
Date: Fri, 1 Dec 2023 21:00:33 +0000 [thread overview]
Message-ID: <ZWpJcS7aJmnRm1CB@kekkonen.localdomain> (raw)
In-Reply-To: <20231124093011.2095073-4-tomm.merciai@gmail.com>
Hi Tommaso,
A few more comments below...
On Fri, Nov 24, 2023 at 10:30:07AM +0100, Tommaso Merciai wrote:
...
> +static int alvium_get_bcrm_vers(struct alvium_dev *alvium)
> +{
> + struct device *dev = &alvium->i2c_client->dev;
> + struct alvium_bcrm_vers *v;
> + u64 val;
> + int ret;
> +
> + ret = alvium_read(alvium, REG_BCRM_VERSION_R, &val, NULL);
> + if (ret)
> + return ret;
> +
> + v = (struct alvium_bcrm_vers *)&val;
You're still reading the entire struct using a single read. :-( This won't
work on a BE machine as while the struct fields are in the same memory
locations, the respective data in a single 64-bit value is not.
> +
> + dev_info(dev, "bcrm version: %u.%u\n", v->minor, v->major);
> +
> + return 0;
> +}
> +
> +static int alvium_get_fw_version(struct alvium_dev *alvium)
> +{
> + struct device *dev = &alvium->i2c_client->dev;
> + struct alvium_fw_vers *fw_v;
> + u64 val;
> + int ret;
> +
> + ret = alvium_read(alvium, REG_BCRM_DEVICE_FIRMWARE_VERSION_R, &val, NULL);
> + if (ret)
> + return ret;
> +
> + fw_v = (struct alvium_fw_vers *)&val;
Same here.
> +
> + dev_info(dev, "fw version: %u.%u.%u.%u\n", fw_v->special, fw_v->major,
> + fw_v->minor, fw_v->patch);
> +
> + return 0;
> +}
> +
> +static int alvium_get_bcrm_addr(struct alvium_dev *alvium)
> +{
> + u64 val;
> + int ret;
> +
> + ret = alvium_read(alvium, REG_BCRM_REG_ADDR_R, &val, NULL);
> + if (ret)
> + return ret;
> +
> + alvium->bcrm_addr = val;
> +
> + return 0;
> +}
...
> +static int alvium_setup_mipi_fmt(struct alvium_dev *alvium)
> +{
> + unsigned int avail_fmt_cnt = 0;
> + unsigned int fmt = 0;
> + size_t sz = 0;
> +
> + alvium->alvium_csi2_fmt = NULL;
This seems to be unnnecessary: the field is assigned below without using it
(obviously).
> +
> + /* calculate fmt array size */
> + for (fmt = 0; fmt < ALVIUM_NUM_SUPP_MIPI_DATA_FMT; fmt++) {
> + if (!alvium->is_mipi_fmt_avail[alvium_csi2_fmts[fmt].fmt_av_bit])
> + continue;
> +
> + if ((!alvium_csi2_fmts[fmt].is_raw) ||
> + (alvium->is_bay_avail[alvium_csi2_fmts[fmt].bay_av_bit]))
> + sz++;
> + }
> +
> + /* init alvium_csi2_fmt array */
> + alvium->alvium_csi2_fmt_n = sz;
> + alvium->alvium_csi2_fmt =
> + kmalloc_array(sz, sizeof(struct alvium_pixfmt), GFP_KERNEL);
> + if (!alvium->alvium_csi2_fmt)
> + return -ENOMEM;
> +
> + /* Create the alvium_csi2 fmt array from formats available */
> + for (fmt = 0; fmt < ALVIUM_NUM_SUPP_MIPI_DATA_FMT; fmt++) {
> + if (!alvium->is_mipi_fmt_avail[alvium_csi2_fmts[fmt].fmt_av_bit])
> + continue;
> +
> + if ((!alvium_csi2_fmts[fmt].is_raw) ||
> + (alvium->is_bay_avail[alvium_csi2_fmts[fmt].bay_av_bit])) {
> + alvium->alvium_csi2_fmt[avail_fmt_cnt] = alvium_csi2_fmts[fmt];
> + avail_fmt_cnt++;
> + }
> + }
> +
> + return 0;
> +}
...
> +static const struct alvium_pixfmt *
> +alvium_code_to_pixfmt(struct alvium_dev *alvium, u32 code)
> +{
> + const struct alvium_pixfmt *formats = alvium->alvium_csi2_fmt;
I'd use alvium->alvium_csi2_fmt and not add a local variable. Up to you.
> + unsigned int i;
> +
> + for (i = 0; formats[i].code; ++i)
> + if (formats[i].code == code)
> + return &formats[i];
> +
> + return &formats[0];
> +}
> +
> +static int alvium_set_mode(struct alvium_dev *alvium,
> + struct v4l2_subdev_state *state)
> +{
> + struct v4l2_mbus_framefmt *fmt;
> + struct v4l2_rect *crop;
> + int ret;
> +
> + crop = v4l2_subdev_state_get_crop(state, 0);
> + fmt = v4l2_subdev_state_get_format(state, 0);
> +
> + v4l_bound_align_image(&fmt->width, alvium->img_min_width,
> + alvium->img_max_width, 0,
> + &fmt->height, alvium->img_min_height,
> + alvium->img_max_height, 0, 0);
> +
> + /* alvium don't accept negative crop left/top */
> + crop->left = clamp((u32)max(0, crop->left), alvium->min_offx,
> + (u32)(alvium->img_max_width - fmt->width));
> + crop->top = clamp((u32)max(0, crop->top), alvium->min_offy,
> + (u32)(alvium->img_max_height - fmt->height));
> +
> + ret = alvium_set_img_width(alvium, fmt->width);
> + if (ret)
> + return ret;
> +
> + ret = alvium_set_img_height(alvium, fmt->height);
> + if (ret)
> + return ret;
> +
> + ret = alvium_set_img_offx(alvium, crop->left);
> + if (ret)
> + return ret;
> +
> + ret = alvium_set_img_offy(alvium, crop->top);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2023-12-01 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 9:30 [PATCH v14 0/3] " Tommaso Merciai
2023-11-24 9:30 ` [PATCH v14 1/3] dt-bindings: vendor-prefixes: Add prefix alliedvision Tommaso Merciai
2023-11-24 9:30 ` [PATCH v14 2/3] media: dt-bindings: alvium: add document YAML binding Tommaso Merciai
2023-11-24 9:30 ` [PATCH v14 3/3] media: i2c: Add support for alvium camera Tommaso Merciai
2023-12-01 21:00 ` Sakari Ailus [this message]
2023-12-02 9:32 ` Tommaso Merciai
2023-12-04 9:30 ` Sakari Ailus
2023-12-04 9:32 ` Tommaso Merciai
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=ZWpJcS7aJmnRm1CB@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bingbu.cao@intel.com \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=djrscally@gmail.com \
--cc=gerald.loacker@wolfvision.net \
--cc=hdegoede@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxfancy@googlegroups.com \
--cc=martin.hecht@avnet.eu \
--cc=mchehab@kernel.org \
--cc=mhecht73@gmail.com \
--cc=michael.roeder@avnet.eu \
--cc=nicholas@rothemail.net \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tomm.merciai@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®