From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: sakari.ailus@iki.fi, jacopo@jmondi.org, paul.j.murphy@intel.com,
daniele.alessandrelli@intel.com, mchehab@kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org
Cc: dmitry.baryshkov@linaro.org, konrad.dybcio@somainline.org,
andrey.konovalov@linaro.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: [PATCH 0/2] Add imx577 compatible to imx412
Date: Tue, 7 Jun 2022 14:40:55 +0100 [thread overview]
Message-ID: <20220607134057.2427663-1-bryan.odonoghue@linaro.org> (raw)
Right now the imx412 and imx577 are code and pin compatible however, they
are distinct pieces of silicon.
Document imx577 as a compatible enum and add the compat string to imx412.c.
This allows us to differentiate these chips in DTS and potentially to apply
any future imx412 or imx577 specific changes appropriately.
Bryan O'Donoghue (2):
media: dt-bindings: imx412: Add imx577 compatible string
media: i2c: imx412: Add imx577 compatible string
Documentation/devicetree/bindings/media/i2c/sony,imx412.yaml | 5 ++++-
drivers/media/i2c/imx412.c | 1 +
2 files changed, 5 insertions(+), 1 deletion(-)
--
2.36.1
next reply other threads:[~2022-06-07 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:40 Bryan O'Donoghue [this message]
2022-06-07 13:40 ` [PATCH 1/2] media: dt-bindings: imx412: Add imx577 compatible string Bryan O'Donoghue
2022-06-09 20:15 ` Rob Herring
2022-06-14 7:48 ` Kieran Bingham
2022-06-07 13:40 ` [PATCH 2/2] media: i2c: " Bryan O'Donoghue
2022-06-14 7:47 ` Kieran Bingham
2022-06-14 8:02 ` Alessandrelli, Daniele
2022-06-14 12:00 ` Sakari Ailus
2022-06-14 14:43 ` Bryan O'Donoghue
2022-06-07 21:56 ` [PATCH 0/2] Add imx577 compatible to imx412 Kieran Bingham
2022-06-07 22:01 ` Bryan O'Donoghue
2022-06-14 12:05 ` 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=20220607134057.2427663-1-bryan.odonoghue@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).