From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Resend: PATCH v2 1/4] Documentation: dt: soc: move driver description to a separate document
Date: Tue, 13 Oct 2015 16:31:02 +0200 [thread overview]
Message-ID: <5224426.GUQgmoMZFj@wuerfel> (raw)
In-Reply-To: <1444679700-11451-1-git-send-email-m-karicheri2@ti.com>
On Monday 12 October 2015 15:54:59 Murali Karicheri wrote:
> Currently the DT bindings have details about the driver as well. This
> patch moves this to a separate document for knav qmss driver so that
> driver detail update can be done as needed without polluting the DT
> bindings description.
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
> ---
> Documentation/arm/keystone/knav-qmss.txt | 24 ++++++++++++++++++++++
> .../bindings/soc/ti/keystone-navigator-qmss.txt | 20 ++++--------------
> 2 files changed, 28 insertions(+), 16 deletions(-)
> create mode 100644 Documentation/arm/keystone/knav-qmss.txt
>
> diff --git a/Documentation/arm/keystone/knav-qmss.txt b/Documentation/arm/keystone/knav-qmss.txt
> new file mode 100644
> index 0000000..79946d1
> --- /dev/null
> +++ b/Documentation/arm/keystone/knav-qmss.txt
>
> +For details of the driver, please refer to
> +Documentation/arm/keystone/knav-qmss.txt
>
> Required properties:
> - compatible : Must be "ti,keystone-navigator-qmss";
>
I'd actually not even put this sentence in: the binding is supposed
to describe the hardware, not the Linux implementation as you correctly
describe above, but I'd also try to not reference files that only
exist in the Linux kernel tree.
Arnd
prev parent reply other threads:[~2015-10-13 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 19:54 [Resend: PATCH v2 1/4] Documentation: dt: soc: move driver description to a separate document Murali Karicheri
2015-10-12 19:55 ` [Resend: PATCH v2 4/4] soc: ti: qmss: make acc queue support optional in the driver Murali Karicheri
2015-10-13 14:31 ` Arnd Bergmann [this message]
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=5224426.GUQgmoMZFj@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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