From: Rob Herring <robh@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: devicetree@vger.kernel.org, linux@rempel-privat.de,
shawnguo@kernel.org, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de, s.hauer@pengutronix.de,
wolfram@the-dreams.de, festevam@gmail.com, Linux-imx@nxp.com,
robh+dt@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/2] dt-bindings: i2c: Convert imx i2c to json-schema
Date: Thu, 9 Jul 2020 17:25:15 -0600 [thread overview]
Message-ID: <20200709232515.GA1093270@bogus> (raw)
In-Reply-To: <1592279454-32551-2-git-send-email-Anson.Huang@nxp.com>
On Tue, 16 Jun 2020 11:50:54 +0800, Anson Huang wrote:
> Convert the i.MX I2C binding to DT schema format using json-schema,
> some improvements applied, such as update example based on latest DT
> file, add more compatible for existing SoCs, and remove unnecessary
> common property "pinctrl".
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> Changes since V2:
> - remove 'clock-frequency' property's type and use enum for it, ONLY support 100KHz/400KHz.
> - remove *-gpios's typs/description, since it is already defined in i2c-gpio.yaml.
> - fix space issue in example.
> ---
> Documentation/devicetree/bindings/i2c/i2c-imx.txt | 49 ----------
> Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 103 +++++++++++++++++++++
> 2 files changed, 103 insertions(+), 49 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-imx.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/i2c-imx.yaml
>
Applied, thanks!
next prev parent reply other threads:[~2020-07-09 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 3:50 [PATCH V3 1/2] dt-bindings: i2c: Convert mxs i2c to json-schema Anson Huang
2020-06-16 3:50 ` [PATCH V3 2/2] dt-bindings: i2c: Convert imx " Anson Huang
2020-07-09 23:25 ` Rob Herring [this message]
2020-07-09 23:24 ` [PATCH V3 1/2] dt-bindings: i2c: Convert mxs " Rob Herring
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=20200709232515.GA1093270@bogus \
--to=robh@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wolfram@the-dreams.de \
/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).