All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.Li@nxp.com>, Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev
Subject: Re: [PATCH v4 1/8] dt-bindings: mmc: Convert fsl-esdhc.txt to yaml
Date: Wed, 12 Jun 2024 08:30:34 +0200	[thread overview]
Message-ID: <7ea69c8d-d3ba-41e3-bcde-cd10274ff498@kernel.org> (raw)
In-Reply-To: <20240611-ls_waring_esdhc-v4-1-d0d8a5b3f3cb@nxp.com>

On 11/06/2024 18:01, Frank Li wrote:
> Convert layerscape fsl-esdhc binding doc from txt to yaml format.
> 
> Addtional change during convert:
> - Deprecate "sdhci,wp-inverted", "sdhci,1-bit-only".
> - Add "reg" and "interrupts" property.
> - Change example "sdhci@2e000" to "mmc@2e000".
> - Compatible string require fsl,<chip>-esdhc followed by fsl,esdhc to match
> most existed dts file.
> - Set clock-frequency to 100mhz in example.
> - clock-frequency is not required now.
> - Allow dma-coherence
> - Add clocks
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> 

This should be reversed with the second patch, because first you fix
voltage-ranges to the same type, then you use it.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2024-06-12  6:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 16:01 [PATCH v4 0/8] arm64: dts: convert fsl,esdhc.txt to yaml and fix layerscape dts warning Frank Li
2024-06-11 16:01 ` Frank Li
2024-06-11 16:01 ` [PATCH v4 1/8] dt-bindings: mmc: Convert fsl-esdhc.txt to yaml Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-12  6:30   ` Krzysztof Kozlowski [this message]
2024-06-11 16:01 ` [PATCH v4 2/8] dt-bindings: mmc: mmc-spi-slot: Change voltage-ranges to uint32-matrix Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 20:23   ` Rob Herring
2024-06-12 14:36     ` Frank Li
2024-06-13  6:35       ` Krzysztof Kozlowski
2024-06-11 16:01 ` [PATCH v4 3/8] arm64: dts: ls1012a: Chang node name from 'esdhc' to 'mmc' Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 16:01 ` [PATCH v4 4/8] arm64: dts: ls1043a: " Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 16:01 ` [PATCH v4 5/8] arm64: dts: ls1046a: " Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 16:01 ` [PATCH v4 6/8] arm64: dts: ls1088a: " Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 16:01 ` [PATCH v4 7/8] arm64: dts: ls208ax: " Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 16:01 ` [PATCH v4 8/8] arm64: dts: lx2160a: " Frank Li
2024-06-11 16:01   ` Frank Li
2024-06-11 18:48 ` [PATCH v4 0/8] arm64: dts: convert fsl,esdhc.txt to yaml and fix layerscape dts warning Dragan Simic
2024-06-11 20:16 ` Rob Herring
2024-06-12  6:31   ` Krzysztof Kozlowski

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=7ea69c8d-d3ba-41e3-bcde-cd10274ff498@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=robh@kernel.org \
    --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 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.