From: Andreas Kemnade <andreas@kemnade.info>
To: Charan Pedumuru <charan.pedumuru@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Barker <paul.barker@sancloud.com>,
Marc Murphy <marc.murphy@sancloud.com>,
Tony Lindgren <tony@atomide.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm: dts: ti: omap: Drop unnecessary or unused properties
Date: Mon, 8 Sep 2025 19:43:24 +0200 [thread overview]
Message-ID: <20250908194324.5d30155e@akair> (raw)
In-Reply-To: <20250908-ti-sdhci-omap-v2-1-72927890482f@gmail.com>
Am Mon, 08 Sep 2025 16:17:12 +0000
schrieb Charan Pedumuru <charan.pedumuru@gmail.com>:
> Remove unnecessary properties like ti,needs-special-reset,
> ti,needs-special-hs-handling and cap-mmc-dual-data-rate from the DTS
> files as there is no user of them.
>
> Signed-off-by: Charan Pedumuru <charan.pedumuru@gmail.com>
Nack. At least ti,needs-special-reset and ti,needs-special-hs-handling
are used by the drivers/mmc/host/omap_hsmmc.c and you remove it from
nodes using compatibles of that driver. So at least restrict that to
sdhci-omap stuff.
Regards,
Andreas
next prev parent reply other threads:[~2025-09-08 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 16:17 [PATCH v2 0/2] dt-bindings: mmc: ti,omap2430-sdhci: Add json schema for the text binding Charan Pedumuru
2025-09-08 16:17 ` [PATCH v2 1/2] arm: dts: ti: omap: Drop unnecessary or unused properties Charan Pedumuru
2025-09-08 17:43 ` Andreas Kemnade [this message]
2025-09-09 7:20 ` Krzysztof Kozlowski
2025-09-13 15:10 ` Charan Pedumuru
2025-09-13 18:49 ` Charan Pedumuru
2025-09-14 22:23 ` Rob Herring
2025-09-20 6:21 ` Charan Pedumuru
2025-09-08 16:17 ` [PATCH v2 2/2] dt-bindings: mmc: sdhci-omap: convert to DT schema Charan Pedumuru
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=20250908194324.5d30155e@akair \
--to=andreas@kemnade.info \
--cc=charan.pedumuru@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.murphy@sancloud.com \
--cc=paul.barker@sancloud.com \
--cc=robh@kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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).