From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com
Subject: [PATCH 1/1] ARM: dts: n9, n950: Remove nokia,nvm-size property
Date: Fri, 4 Sep 2020 09:58:11 +0300 [thread overview]
Message-ID: <20200904065811.9312-1-sakari.ailus@linux.intel.com> (raw)
Remove nokia,nvm-size property as it is no longer needed. The driver can
nowadays figure out the size so do not specify it in DT.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
Hi Tony,
Commit 33e17ea2d4f0 ("media: dt-bindings: smia: Remove documentation of
nokia,nvm-size") removed this from DT bindings and the driver support was
added by 941e1d36b5b6 ("media: smiapp: Support probing NVM size"). So we
can remove it from here, too, I think.
arch/arm/boot/dts/omap3-n9.dts | 1 -
arch/arm/boot/dts/omap3-n950.dts | 1 -
2 files changed, 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-n9.dts b/arch/arm/boot/dts/omap3-n9.dts
index 2495a696cec6..d211bcc31174 100644
--- a/arch/arm/boot/dts/omap3-n9.dts
+++ b/arch/arm/boot/dts/omap3-n9.dts
@@ -23,7 +23,6 @@ smia_1: camera@10 {
vana-supply = <&vaux3>;
clocks = <&isp 0>;
clock-frequency = <9600000>;
- nokia,nvm-size = <(16 * 64)>;
flash-leds = <&as3645a_flash &as3645a_indicator>;
port {
smia_1_1: endpoint {
diff --git a/arch/arm/boot/dts/omap3-n950.dts b/arch/arm/boot/dts/omap3-n950.dts
index 31d47a1fad84..1bac51e9a79e 100644
--- a/arch/arm/boot/dts/omap3-n950.dts
+++ b/arch/arm/boot/dts/omap3-n950.dts
@@ -76,7 +76,6 @@ smia_1: camera@10 {
vana-supply = <&vaux3>;
clocks = <&isp 0>;
clock-frequency = <9600000>;
- nokia,nvm-size = <(16 * 64)>;
flash-leds = <&as3645a_flash &as3645a_indicator>;
port {
smia_1_1: endpoint {
--
2.27.0
next reply other threads:[~2020-09-04 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 6:58 Sakari Ailus [this message]
2020-09-10 9:44 ` [PATCH 1/1] ARM: dts: n9, n950: Remove nokia,nvm-size property Tony Lindgren
2020-09-11 10:20 ` 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=20200904065811.9312-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).