devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
	linux-samsung-soc@vger.kernel.org, Wolfram Sang <wsa@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: i2c: samsung,s3c2410-i2c: convert to dtschema
Date: Mon, 7 Feb 2022 13:18:46 -0600	[thread overview]
Message-ID: <YgFwlgXnHTIUVeOH@robh.at.kernel.org> (raw)
In-Reply-To: <20220131172713.208976-1-krzysztof.kozlowski@canonical.com>

On Mon, 31 Jan 2022 18:27:13 +0100, Krzysztof Kozlowski wrote:
> Convert the Samsung S3C24xx/S3C64xx/S5PV210/Exynos SoC I2C Controller
> bindings to DT schema format.
> 
> The conversion includes also changes/fixes to the bindings, matching the
> real hardware and existing Linux driver:
> 1. Do not require interrupts on samsung,exynos5-sata-phy-i2c, because
>    there is no such.
> 2. Do not allow gpios on samsung,exynos5-sata-phy-i2c, because they are
>    hard-wired just like for HDMI phy.
> 3. Do not require samsung,i2c-sda-delay and use default of 0.
> 4. Require clock, which was always required but missing in bindings.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
>  .../devicetree/bindings/i2c/i2c-s3c2410.txt   |  58 -------
>  .../bindings/i2c/samsung,s3c2410-i2c.yaml     | 164 ++++++++++++++++++
>  2 files changed, 164 insertions(+), 58 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt
>  create mode 100644 Documentation/devicetree/bindings/i2c/samsung,s3c2410-i2c.yaml
> 

Applied, thanks!

      reply	other threads:[~2022-02-07 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 17:27 [PATCH] dt-bindings: i2c: samsung,s3c2410-i2c: convert to dtschema Krzysztof Kozlowski
2022-02-07 19:18 ` Rob Herring [this message]

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=YgFwlgXnHTIUVeOH@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=wsa@kernel.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).