From: Rahul Tanwar <rahul.tanwar@linux.intel.com>
To: robh+dt@kernel.org, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, mark.rutland@arm.com,
linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com,
qi-ming.wu@intel.com, cheol.yong.kim@intel.com,
rahul.tanwar@intel.com,
Rahul Tanwar <rahul.tanwar@linux.intel.com>
Subject: [PATCH v3 0/2] dt-bindings: serial: lantiq: Convert to YAML & add support for new SoC
Date: Wed, 21 Aug 2019 15:06:50 +0800 [thread overview]
Message-ID: <cover.1566370151.git.rahul.tanwar@linux.intel.com> (raw)
There is a new product which reuses Lantiq serial controller IP. Patch 1 in this
series converts existing lantiq dt bindings to YAML schema and Patch 2 updates
it to support newer product.
These patches are baselined upon Linux 5.3-rc4 at below Git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
v3:
* Use compatible name for filename.
* Use if/then schema to describe a property which is different for each
compatibles.
* Address other review concerns about YAML format.
v2:
* Update license to GPL-2.0-only.
* Fix trailing whitespace error.
Rahul Tanwar (2):
dt-bindings: serial: lantiq: Convert to YAML schema
dt-bindings: lantiq: Update for new SoC
.../devicetree/bindings/serial/lantiq,asc.yaml | 90 ++++++++++++++++++++++
.../devicetree/bindings/serial/lantiq_asc.txt | 31 --------
2 files changed, 90 insertions(+), 31 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial/lantiq,asc.yaml
delete mode 100644 Documentation/devicetree/bindings/serial/lantiq_asc.txt
--
2.11.0
next reply other threads:[~2019-08-21 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 7:06 Rahul Tanwar [this message]
2019-08-21 7:06 ` [PATCH v3 1/2] dt-bindings: serial: lantiq: Convert to YAML schema Rahul Tanwar
2019-08-27 17:21 ` Rob Herring
2019-08-27 17:21 ` Rob Herring
2019-08-21 7:06 ` [PATCH v3 2/2] dt-bindings: lantiq: Update for new SoC Rahul Tanwar
2019-08-27 17:22 ` Rob Herring
2019-08-27 17:22 ` 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=cover.1566370151.git.rahul.tanwar@linux.intel.com \
--to=rahul.tanwar@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=qi-ming.wu@intel.com \
--cc=rahul.tanwar@intel.com \
--cc=robh+dt@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 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.