From: haibo.chen@nxp.com
To: adrian.hunter@intel.com, ulf.hansson@linaro.org,
linux-mmc@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: linux-imx@nxp.com, haibo.chen@nxp.com, kernel@pengutronix.de,
festevam@gmail.com, cniedermaier@dh-electronics.com,
devicetree@vger.kernel.org, kernel@dh-electronics.com
Subject: [PATCH 3/4] dt-bindings: mmc: fsl-imx-esdhc: remove property "fsl,wp-controller"
Date: Fri, 5 May 2023 16:49:54 +0800 [thread overview]
Message-ID: <20230505084955.238940-3-haibo.chen@nxp.com> (raw)
In-Reply-To: <20230505084955.238940-1-haibo.chen@nxp.com>
From: Haibo Chen <haibo.chen@nxp.com>
Driver do not use this property, so remove it here.
Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
---
Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
index fbfd822b9270..831eadecc7e4 100644
--- a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
+++ b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
@@ -96,11 +96,6 @@ properties:
interrupts:
maxItems: 1
- fsl,wp-controller:
- description: |
- boolean, if present, indicate to use controller internal write protection.
- type: boolean
-
fsl,delay-line:
$ref: /schemas/types.yaml#/definitions/uint32
description: |
--
2.34.1
next prev parent reply other threads:[~2023-05-05 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:49 [PATCH 1/4] mmc: sdhci-esdhc-imx: remove unused enum cd_types haibo.chen
2023-05-05 8:49 ` [PATCH 2/4] mmc: sdhci-esdhc-imx: remove redundant write protect code haibo.chen
2023-05-05 8:49 ` haibo.chen [this message]
2023-05-05 9:33 ` [PATCH 3/4] dt-bindings: mmc: fsl-imx-esdhc: remove property "fsl,wp-controller" Rob Herring
2023-05-05 10:04 ` Bough Chen
2023-05-05 8:49 ` [PATCH 4/4] arm: dts: imx: remove "fsl,wp-controller" since it is dropped haibo.chen
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=20230505084955.238940-3-haibo.chen@nxp.com \
--to=haibo.chen@nxp.com \
--cc=adrian.hunter@intel.com \
--cc=cniedermaier@dh-electronics.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-imx@nxp.com \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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).