LKML Archive on
help / color / mirror / Atom feed
From: Paul Walmsley <>
Cc: Mark Rutland <>,
	Pawel Moll <>,
	Ian Campbell <>,
	Jonathan Corbet <>,, Rob Herring <>,
	Paul Walmsley <>,
	Kumar Gala <>,
	Javier Martinez Canillas <>
Subject: [PATCH v2 1/3] Documentation: DT: document compatible string existence requirement
Date: Fri, 30 Jan 2015 15:11:04 -0700	[thread overview]
Message-ID: <20150130221104.4761.59173.stgit@dusk.lan> (raw)
In-Reply-To: <20150130221104.4761.50643.stgit@dusk.lan>

DT maintainers require all compatible strings used in chip or board
DTS file to be previously documented somewhere in
Documentation/devicetree/bindings, per:

Document this requirement in the DT patch submission requirements
text file.

This second version updates the documentation to align with
Rob's comments here:

Signed-off-by: Paul Walmsley <>
Cc: Rob Herring <>
Cc: Pawel Moll <>
Cc: Mark Rutland <>
Cc: Ian Campbell <>
Cc: Kumar Gala <>
Cc: Javier Martinez Canillas <>
Cc: Jonathan Corbet <>
Cc: Paul Walmsley <>
 .../devicetree/bindings/submitting-patches.txt     |   23 ++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/Documentation/devicetree/bindings/submitting-patches.txt b/Documentation/devicetree/bindings/submitting-patches.txt
index b7ba01ad1426..56742bc70218 100644
--- a/Documentation/devicetree/bindings/submitting-patches.txt
+++ b/Documentation/devicetree/bindings/submitting-patches.txt
@@ -15,6 +15,29 @@ I. For patch submitters
   3) The Documentation/ portion of the patch should come in the series before
      the code implementing the binding.
+  4) Any compatible strings used in a chip or board DTS file must be
+     previously documented in the corresponding DT binding text file
+     in Documentation/devicetree/bindings.  This rule applies even if
+     the Linux device driver does not yet match on the compatible
+     string.  [ checkpatch will emit warnings if this step is not
+     followed as of commit bff5da4335256513497cc8c79f9a9d1665e09864
+     ("checkpatch: add DT compatible string documentation checks"). ]
+  5) The wildcard "<chip>" may be used in compatible strings, as in
+     the following example:
+         - compatible: Must contain '"nvidia,<chip>-pcie",
+           "nvidia,tegra20-pcie"' where <chip> is tegra30, tegra132, ...
+     As in the above example, the known values of "<chip>" should be
+     documented if it is used.
+  6) If a documented compatible string is not yet matched by the
+     driver, the documentation should also include a compatible
+     string that is matched by the driver (as in the "nvidia,tegra20-pcie"
+     example above).
 II. For kernel maintainers
   1) If you aren't comfortable reviewing a given binding, reply to it and ask

  parent reply	other threads:[~2015-01-30 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 22:11 [PATCH v2 0/3] Documentation: DT bindings: update DT binding docs with Tegra chips Paul Walmsley
2015-01-30 22:11 ` [PATCH v2 3/3] Documentation: DT bindings: add nvidia, tegra132-denver compatible string Paul Walmsley
2015-01-30 22:11 ` Paul Walmsley [this message]
2015-01-30 22:11 ` [PATCH v2 2/3] Documentation: DT bindings: add more Tegra chip compatible strings Paul Walmsley
2015-01-31 19:28   ` Eduardo Valentin
2015-02-05 19:25   ` Wolfram Sang
2015-02-04  2:36 ` [PATCH v2 0/3] Documentation: DT bindings: update DT binding docs with Tegra chips 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150130221104.4761.59173.stgit@dusk.lan \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH v2 1/3] Documentation: DT: document compatible string existence requirement' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).