From: Rob Herring <robh@kernel.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Mark Rutland <mark.rutland@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
krzk@kernel.org, Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH 2/4] dt-bindings: sram: Allow for more specific compatibles
Date: Tue, 17 Dec 2019 19:42:39 -0600 [thread overview]
Message-ID: <20191218014239.GA31784@bogus> (raw)
In-Reply-To: <20191209093441.50694-2-maxime@cerno.tech>
On Mon, 9 Dec 2019 10:34:39 +0100, Maxime Ripard wrote:
> Even though the generic mmio-sram binding has a list of the sections
> compatible allowed, most device trees have more specific compatibles
> attached to those generic ones.
>
> This creates warnings at the moment, and we don't really want to cripple
> the generic binding with all the vendor specific combinations that would
> prove to be hard to maintain.
>
> Let's allow additional compatibles for the sections, and then we can have
> the vendor-specific bindings to reduce the scope of what's allowed exactly.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
> .../devicetree/bindings/sram/sram.yaml | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
Applied, thanks.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.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>,
krzk@kernel.org, Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH 2/4] dt-bindings: sram: Allow for more specific compatibles
Date: Tue, 17 Dec 2019 19:42:39 -0600 [thread overview]
Message-ID: <20191218014239.GA31784@bogus> (raw)
In-Reply-To: <20191209093441.50694-2-maxime@cerno.tech>
On Mon, 9 Dec 2019 10:34:39 +0100, Maxime Ripard wrote:
> Even though the generic mmio-sram binding has a list of the sections
> compatible allowed, most device trees have more specific compatibles
> attached to those generic ones.
>
> This creates warnings at the moment, and we don't really want to cripple
> the generic binding with all the vendor specific combinations that would
> prove to be hard to maintain.
>
> Let's allow additional compatibles for the sections, and then we can have
> the vendor-specific bindings to reduce the scope of what's allowed exactly.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
> .../devicetree/bindings/sram/sram.yaml | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
Applied, thanks.
Rob
_______________________________________________
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-12-18 1:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 9:34 [PATCH 1/4] dt-bindings: sram: Allow for the childs nodes to be called sections Maxime Ripard
2019-12-09 9:34 ` Maxime Ripard
2019-12-09 9:34 ` [PATCH 2/4] dt-bindings: sram: Allow for more specific compatibles Maxime Ripard
2019-12-09 9:34 ` Maxime Ripard
2019-12-18 1:42 ` Rob Herring [this message]
2019-12-18 1:42 ` Rob Herring
2019-12-09 9:34 ` [PATCH 3/4] dt-bindings: sram: Add Allwinner SRAM compatibles Maxime Ripard
2019-12-09 9:34 ` Maxime Ripard
2019-12-18 1:42 ` Rob Herring
2019-12-18 1:42 ` Rob Herring
2019-12-09 9:34 ` [PATCH 4/4] dt-bindings: sram: Convert Allwinner A10 system controller to a schema Maxime Ripard
2019-12-09 9:34 ` Maxime Ripard
2019-12-18 1:43 ` Rob Herring
2019-12-18 1:43 ` Rob Herring
2019-12-18 1:50 ` Rob Herring
2019-12-18 1:50 ` Rob Herring
2019-12-18 1:39 ` [PATCH 1/4] dt-bindings: sram: Allow for the childs nodes to be called sections Rob Herring
2019-12-18 1:39 ` 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=20191218014239.GA31784@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maxime@cerno.tech \
--cc=mripard@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 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.