From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: "Alessandrelli, Daniele" <daniele.alessandrelli@intel.com>,
"Murphy, Paul J" <paul.j.murphy@intel.com>,
"jacopo@jmondi.org" <jacopo@jmondi.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"sakari.ailus@iki.fi" <sakari.ailus@iki.fi>
Cc: "konrad.dybcio@somainline.org" <konrad.dybcio@somainline.org>,
"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"andrey.konovalov@linaro.org" <andrey.konovalov@linaro.org>
Subject: Re: [PATCH v2 0/3] Add imx577 compatible to imx412
Date: Thu, 21 Jul 2022 16:24:46 +0100 [thread overview]
Message-ID: <3bfd6b12-cd8f-5697-13db-0e30477e8f35@linaro.org> (raw)
In-Reply-To: <fe14541568ab201abac5cfd4914b750d54ef4aa6.camel@intel.com>
On 21/07/2022 16:15, Alessandrelli, Daniele wrote:
> In the meantime, would you be able to check what 16-bit value the
> imx577 sensor reports at offset 0x0000 (which, on some IMX models,
> seems to be another ID register)?
Looks like it is zero.
[ 10.422064] imx577 20-001a: Register @ 0x0000 0x0000 register @
0x0016 0x0577
next prev parent reply other threads:[~2022-07-21 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 1:42 [PATCH v2 0/3] Add imx577 compatible to imx412 Bryan O'Donoghue
2022-07-18 1:42 ` [PATCH v2 1/3] media: dt-bindings: media: Rename imx412 to imx577 Bryan O'Donoghue
2022-07-20 22:31 ` Rob Herring
2022-07-22 16:03 ` Sakari Ailus
2022-07-22 16:47 ` Bryan O'Donoghue
2022-07-18 1:42 ` [PATCH v2 2/3] media: i2c: imx577: Rename imx412.c to imx577.c Bryan O'Donoghue
2022-07-18 1:42 ` [PATCH v2 3/3] media: i2c: imx577: Fix chip identifier define name Bryan O'Donoghue
2022-07-21 15:15 ` [PATCH v2 0/3] Add imx577 compatible to imx412 Alessandrelli, Daniele
2022-07-21 15:24 ` Bryan O'Donoghue [this message]
2022-07-27 20:12 ` Alessandrelli, Daniele
2022-07-28 2:01 ` Bryan O'Donoghue
2022-07-28 11:41 ` sakari.ailus
2022-07-28 12:05 ` Bryan O'Donoghue
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=3bfd6b12-cd8f-5697-13db-0e30477e8f35@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andrey.konovalov@linaro.org \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jacopo@jmondi.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@intel.com \
--cc=sakari.ailus@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).