From: shravan kumar <shravan.chippa@microchip.com>
To: <paul.j.murphy@intel.com>, <daniele.alessandrelli@intel.com>,
<mchehab@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <shawnguo@kernel.org>,
<s.hauer@pengutronix.de>
Cc: <kernel@pengutronix.de>, <festevam@gmail.com>,
<linux-imx@nxp.com>, <linux-media@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<shravan.chippa@microchip.com>,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: [PATCH v11 4/5] dt-bindings: media: i2c: imx334 add new link_freq
Date: Wed, 8 Feb 2023 10:39:14 +0530 [thread overview]
Message-ID: <20230208050915.1958183-5-shravan.chippa@microchip.com> (raw)
In-Reply-To: <20230208050915.1958183-1-shravan.chippa@microchip.com>
From: Shravan Chippa <shravan.chippa@microchip.com>
Add new supported link frequency in dt example.
Suggested-by: Sakari Ailus <sakari.ailus@iki.fi>
Signed-off-by: Shravan Chippa <shravan.chippa@microchip.com>
---
Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml b/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml
index f5055b9db693..09533496b20c 100644
--- a/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml
@@ -82,7 +82,7 @@ examples:
imx334: endpoint {
remote-endpoint = <&cam>;
data-lanes = <1 2 3 4>;
- link-frequencies = /bits/ 64 <891000000>;
+ link-frequencies = /bits/ 64 <891000000 445500000>;
};
};
};
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-08 5:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 5:09 [PATCH v11 0/5] media: i2c: imx334: support lower bandwidth mode shravan kumar
2023-02-08 5:09 ` [PATCH v11 1/5] media: i2c: imx334: replace __v4l2_ctrl_s_ctrl to __v4l2_ctrl_modify_range shravan kumar
2023-02-08 5:09 ` [PATCH v11 2/5] media: i2c: imx334: add missing reset values for mode 3840x2160_regs[] shravan kumar
2023-02-08 5:09 ` [PATCH v11 3/5] media: i2c: imx334: support lower bandwidth mode shravan kumar
2023-02-22 9:14 ` Sakari Ailus
2023-02-22 9:58 ` Conor Dooley
2023-02-22 10:03 ` Sakari Ailus
2023-02-22 10:06 ` Sakari Ailus
2023-02-22 10:20 ` Shravan.Chippa
2023-02-22 11:32 ` Sakari Ailus
2023-02-24 10:02 ` Shravan.Chippa
2023-02-24 10:51 ` Sakari Ailus
2023-02-08 5:09 ` shravan kumar [this message]
2023-02-08 8:08 ` [PATCH v11 4/5] dt-bindings: media: i2c: imx334 add new link_freq Krzysztof Kozlowski
2023-02-08 5:09 ` [PATCH v11 5/5] media: i2c: imx334: update pixel and link frequency shravan kumar
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=20230208050915.1958183-5-shravan.chippa@microchip.com \
--to=shravan.chippa@microchip.com \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@intel.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@iki.fi \
--cc=shawnguo@kernel.org \
/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).