All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhargav Joshi <j.bhargav.u@gmail.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>,
	 Andreas Kemnade <andreas@kemnade.info>,
	Kevin Hilman <khilman@baylibre.com>,
	 Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>,  Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Alexandre Belloni <alexandre.belloni@bootlin.com>,
	 Keerthy <j-keerthy@ti.com>, Afzal Mohammed <afzal@ti.com>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
	 goledhruva@gmail.com, m-chawdhry@ti.com,
	daniel.baluta@gmail.com,  simona.toaca@nxp.com,
	j.bhargav.u@gmail.com
Subject: [PATCH v3 2/4] ARM: dts: ti: am335x-shc: Remove unused ti,no-init property
Date: Tue, 04 Aug 2026 22:35:06 +0530	[thread overview]
Message-ID: <20260804-ti-omap-rtc-v3-2-ba3bbd8af570@gmail.com> (raw)
In-Reply-To: <20260804-ti-omap-rtc-v3-0-ba3bbd8af570@gmail.com>

The 'ti,no-init' property is a legacy, undocumented boolean property
that is entirely unhandled by the rtc-omap driver.
Remove this unnecessary property from dts.

Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
 arch/arm/boot/dts/ti/omap/am335x-shc.dts | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/arch/arm/boot/dts/ti/omap/am335x-shc.dts b/arch/arm/boot/dts/ti/omap/am335x-shc.dts
index 597482822608..2b946823928f 100644
--- a/arch/arm/boot/dts/ti/omap/am335x-shc.dts
+++ b/arch/arm/boot/dts/ti/omap/am335x-shc.dts
@@ -241,10 +241,6 @@ &mmc3 {
 	status = "okay";
 };
 
-&rtc {
-	ti,no-init;
-};
-
 &sham {
 	status = "okay";
 };

-- 
2.55.0


  parent reply	other threads:[~2026-08-04 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 17:05 [PATCH v3 0/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema and cleanups Bhargav Joshi
2026-08-04 17:05 ` [PATCH v3 1/4] ARM: dts: ti: am57xx-idk-common: Remove unused ext-clk-src property Bhargav Joshi
2026-08-04 17:13   ` sashiko-bot
2026-08-04 17:05 ` Bhargav Joshi [this message]
2026-08-04 17:12   ` [PATCH v3 2/4] ARM: dts: ti: am335x-shc: Remove unused ti,no-init property sashiko-bot
2026-08-04 17:05 ` [PATCH v3 3/4] ARM: dts: omap: dra7: add da830 fallback to am3352 rtc compatible string Bhargav Joshi
2026-08-04 17:16   ` sashiko-bot
2026-08-04 17:05 ` [PATCH v3 4/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema Bhargav Joshi
2026-08-04 17:30   ` sashiko-bot
2026-08-11 17:37   ` Rob Herring (Arm)
2026-08-20 21:29   ` (subset) " Alexandre Belloni
2026-08-31 18:11 ` (subset) [PATCH v3 0/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema and cleanups Kevin Hilman

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=20260804-ti-omap-rtc-v3-2-ba3bbd8af570@gmail.com \
    --to=j.bhargav.u@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=afzal@ti.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=goledhruva@gmail.com \
    --cc=j-keerthy@ti.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=simona.toaca@nxp.com \
    --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 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.