From: Lee Jones <lee.jones@linaro.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: Add syscon YAML description
Date: Mon, 4 Nov 2019 07:15:54 +0000 [thread overview]
Message-ID: <20191104071554.GK5700@dell> (raw)
In-Reply-To: <20191101141034.259906-1-maxime@cerno.tech>
On Fri, 01 Nov 2019, Maxime Ripard wrote:
> The syscon binding is a pretty loose one, with everyone having a bunch of
> vendor specific compatibles.
>
> In order to start the effort to describe them using YAML, let's create a
> binding that tolerates additional, not listed, compatibles.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
> .../devicetree/bindings/mfd/syscon.txt | 32 --------
> .../bindings/misc/allwinner,syscon.txt | 20 -----
> .../devicetree/bindings/misc/syscon.yaml | 74 +++++++++++++++++++
Why are you moving this to drivers/misc?
> 3 files changed, 74 insertions(+), 52 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mfd/syscon.txt
> delete mode 100644 Documentation/devicetree/bindings/misc/allwinner,syscon.txt
> create mode 100644 Documentation/devicetree/bindings/misc/syscon.yaml
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-04 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 14:10 [PATCH] dt-bindings: Add syscon YAML description Maxime Ripard
2019-11-04 7:15 ` Lee Jones [this message]
2019-11-07 21:31 ` Lee Jones
2019-11-06 4:30 ` 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=20191104071554.GK5700@dell \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maxime@cerno.tech \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).