From: Eugeniu Rosca <erosca@de.adit-jv.com> To: Ulf Hansson <ulf.hansson@linaro.org>, Adrian Hunter <adrian.hunter@intel.com>, Wolfram Sang <wsa+renesas@sang-engineering.com>, <linux-mmc@vger.kernel.org> Cc: Linus Walleij <linus.walleij@linaro.org>, Mathieu Malaterre <malat@debian.org>, Pavel Machek <pavel@ucw.cz>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Eugeniu Rosca <erosca@de.adit-jv.com>, Eugeniu Rosca <roscaeugeniu@gmail.com> Subject: [PATCH 1/3] dt-bindings: mmc: Add 'fixed-emmc-driver-type-hs{200,400}' Date: Tue, 5 Nov 2019 06:50:13 +0100 [thread overview] Message-ID: <20191105055015.23656-1-erosca@de.adit-jv.com> (raw) A certain eMMC manufacturer provided below requirement: ---snip--- Use "drive strength" value of 4 or 1 for HS400 or 0 for HS200. ---snip--- The existing "fixed-emmc-driver-type" property [1] is the closest one to implement the above, but it falls short due to being unable to define two values to differentiate between HS200 and HS400 (both modes may be supported by the same non-removable MMC device). To allow users to set a preferred HS200/HS400 "drive strength", provide two more bindings inspired from [1]: - fixed-emmc-driver-type-hs200 - fixed-emmc-driver-type-hs400 For more details about eMMC I/O driver strength types, see Jedec spec. Keep "fixed-emmc-driver-type" in place for backward compatibility. [1] commit 6186d06c519e21 ("mmc: parse new binding for eMMC fixed driver type") Cc: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com> --- .../bindings/mmc/mmc-controller.yaml | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml index 080754e0ef35..1c64b14f91a3 100644 --- a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml +++ b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml @@ -248,6 +248,24 @@ properties: the driver type as specified in the eMMC specification (table 206 in spec version 5.1) + fixed-emmc-driver-type-hs200: + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32 + - minimum: 0 + - maximum: 4 + description: + Same as "fixed-emmc-driver-type", but specific to HS200 mode. + If defined, overrides "fixed-emmc-driver-type" in HS200 mode. + + fixed-emmc-driver-type-hs400: + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32 + - minimum: 0 + - maximum: 4 + description: + Same as "fixed-emmc-driver-type", but specific to HS400 mode. + If defined, overrides "fixed-emmc-driver-type" in HS400 mode. + post-power-on-delay-ms: allOf: - $ref: /schemas/types.yaml#/definitions/uint32 @@ -336,6 +354,8 @@ patternProperties: dependencies: cd-debounce-delay-ms: [ cd-gpios ] fixed-emmc-driver-type: [ non-removable ] + fixed-emmc-driver-type-hs200: [ non-removable ] + fixed-emmc-driver-type-hs400: [ non-removable ] examples: - | -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniu Rosca <erosca@de.adit-jv.com> To: Ulf Hansson <ulf.hansson@linaro.org>, Adrian Hunter <adrian.hunter@intel.com>, Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-mmc@vger.kernel.org Cc: Linus Walleij <linus.walleij@linaro.org>, Mathieu Malaterre <malat@debian.org>, Pavel Machek <pavel@ucw.cz>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Eugeniu Rosca <erosca@de.adit-jv.com>, Eugeniu Rosca <roscaeugeniu@gmail.com> Subject: [PATCH 1/3] dt-bindings: mmc: Add 'fixed-emmc-driver-type-hs{200,400}' Date: Tue, 5 Nov 2019 06:50:13 +0100 [thread overview] Message-ID: <20191105055015.23656-1-erosca@de.adit-jv.com> (raw) A certain eMMC manufacturer provided below requirement: ---snip--- Use "drive strength" value of 4 or 1 for HS400 or 0 for HS200. ---snip--- The existing "fixed-emmc-driver-type" property [1] is the closest one to implement the above, but it falls short due to being unable to define two values to differentiate between HS200 and HS400 (both modes may be supported by the same non-removable MMC device). To allow users to set a preferred HS200/HS400 "drive strength", provide two more bindings inspired from [1]: - fixed-emmc-driver-type-hs200 - fixed-emmc-driver-type-hs400 For more details about eMMC I/O driver strength types, see Jedec spec. Keep "fixed-emmc-driver-type" in place for backward compatibility. [1] commit 6186d06c519e21 ("mmc: parse new binding for eMMC fixed driver type") Cc: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com> --- .../bindings/mmc/mmc-controller.yaml | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml index 080754e0ef35..1c64b14f91a3 100644 --- a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml +++ b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml @@ -248,6 +248,24 @@ properties: the driver type as specified in the eMMC specification (table 206 in spec version 5.1) + fixed-emmc-driver-type-hs200: + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32 + - minimum: 0 + - maximum: 4 + description: + Same as "fixed-emmc-driver-type", but specific to HS200 mode. + If defined, overrides "fixed-emmc-driver-type" in HS200 mode. + + fixed-emmc-driver-type-hs400: + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32 + - minimum: 0 + - maximum: 4 + description: + Same as "fixed-emmc-driver-type", but specific to HS400 mode. + If defined, overrides "fixed-emmc-driver-type" in HS400 mode. + post-power-on-delay-ms: allOf: - $ref: /schemas/types.yaml#/definitions/uint32 @@ -336,6 +354,8 @@ patternProperties: dependencies: cd-debounce-delay-ms: [ cd-gpios ] fixed-emmc-driver-type: [ non-removable ] + fixed-emmc-driver-type-hs200: [ non-removable ] + fixed-emmc-driver-type-hs400: [ non-removable ] examples: - | -- 2.23.0
next reply other threads:[~2019-11-05 5:51 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-05 5:50 Eugeniu Rosca [this message] 2019-11-05 5:50 ` [PATCH 1/3] dt-bindings: mmc: Add 'fixed-emmc-driver-type-hs{200,400}' Eugeniu Rosca 2019-11-05 5:50 ` [PATCH 2/3] mmc: host: Compress 'fixed-emmc-driver-type' handling Eugeniu Rosca 2019-11-05 5:50 ` Eugeniu Rosca 2019-11-05 5:50 ` [PATCH 3/3] mmc: core: Add 'fixed-emmc-driver-type-hs{200,400}' Eugeniu Rosca 2019-11-05 5:50 ` Eugeniu Rosca 2019-11-05 6:22 ` [PATCH 1/3] dt-bindings: mmc: " Wolfram Sang 2019-11-05 8:32 ` Eugeniu Rosca 2019-11-05 8:32 ` Eugeniu Rosca 2019-11-07 0:39 ` Rob Herring 2019-11-12 21:19 ` Wolfram Sang 2019-11-12 23:11 ` Linus Walleij 2019-11-12 23:11 ` Linus Walleij 2019-11-14 10:46 ` Ulf Hansson 2019-11-06 11:07 ` Linus Walleij 2019-11-06 11:07 ` Linus Walleij 2019-11-11 22:25 ` Eugeniu Rosca 2019-11-11 22:25 ` Eugeniu Rosca 2019-11-12 23:08 ` Linus Walleij 2019-11-12 23:08 ` Linus Walleij
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=20191105055015.23656-1-erosca@de.adit-jv.com \ --to=erosca@de.adit-jv.com \ --cc=adrian.hunter@intel.com \ --cc=devicetree@vger.kernel.org \ --cc=linus.walleij@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mmc@vger.kernel.org \ --cc=malat@debian.org \ --cc=pavel@ucw.cz \ --cc=roscaeugeniu@gmail.com \ --cc=ulf.hansson@linaro.org \ --cc=wsa+renesas@sang-engineering.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: linkBe 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.