From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Tarang Raval <tarang.raval@siliconsignals.io>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
"jai.luthra" <jai.luthra@ideasonboard.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Philippe Baetens <philippebaetens@gmail.com>
Subject: Re: [PATCH v5 2/2] media: i2c: mira016: Add driver for Mira016
Date: Thu, 1 Oct 2026 09:51:46 +0300 [thread overview]
Message-ID: <ar4DAkCABRYLHWth@kekkonen.localdomain> (raw)
In-Reply-To: <ar03QZc3wVMKy8F8@zed>
Hi Jacopo,
On Wed, Sep 30, 2026 at 06:34:12PM +0200, Jacopo Mondi wrote:
> > Like for the above array 0xe000 register.
>
> 0xe000 is repeated multiple times because it's the register that
> selects which bank to write to (there are 2 registers banks on this
> sensor)
If you have pages, you should use regmap's page support. See e.g.
<URL:https://lore.kernel.org/linux-media/20261001061250.37734-1-sakari.ailus@linux.intel.com/T/#u>.
There are probably other such examples, too.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-10-01 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 10:51 [PATCH v5 0/2] media: i2c: Add driver for Mira016 Jacopo Mondi
2026-09-30 10:51 ` [PATCH v5 1/2] dt-bindings: media: i2c: Add Mira016 image sensor Jacopo Mondi
2026-09-30 10:51 ` [PATCH v5 2/2] media: i2c: mira016: Add driver for Mira016 Jacopo Mondi
2026-09-30 11:06 ` sashiko-bot
2026-09-30 13:47 ` Tarang Raval
2026-09-30 16:34 ` Jacopo Mondi
2026-10-01 6:51 ` Sakari Ailus [this message]
2026-10-01 6:46 ` Sakari Ailus
2026-10-01 7:19 ` Jacopo Mondi
2026-10-01 7:52 ` Sakari Ailus
2026-10-01 10:07 ` Jacopo Mondi
2026-10-01 10:58 ` 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=ar4DAkCABRYLHWth@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=jai.luthra@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=philippebaetens@gmail.com \
--cc=robh@kernel.org \
--cc=tarang.raval@siliconsignals.io \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.