From: Vinod Koul <vinod.koul@intel.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: dmaengine@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings
Date: Mon, 16 Nov 2015 03:51:52 +0000 [thread overview]
Message-ID: <20151116035533.GC25173@localhost> (raw)
In-Reply-To: <1447293239-8554-1-git-send-email-horms+renesas@verge.net.au>
On Thu, Nov 12, 2015 at 10:53:59AM +0900, Simon Horman wrote:
> In general Renesas hardware is not documented to the extent where the
> relationship between IP blocks on different SoCs can be assumed although
> they may appear to operate the same way. Furthermore the documentation
> typically does not specify a version for individual IP blocks. For these
> reasons a convention of using the SoC name in place of a version and
> providing SoC-specific compat strings has been adopted.
>
> Although not universally liked this convention is used in the bindings for
> most drivers for Renesas hardware. The purpose of this patch is to
> update the Renesas R-Car DMA Controller driver to follow this convention.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2015-11-16 3:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 1:53 [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings Simon Horman
2015-11-12 10:25 ` Geert Uytterhoeven
2015-11-12 23:28 ` Rob Herring
2015-11-13 8:08 ` Geert Uytterhoeven
2015-11-16 3:51 ` Vinod Koul [this message]
2016-01-14 10:09 ` Geert Uytterhoeven
2016-01-18 14:49 ` Vinod Koul
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=20151116035533.GC25173@localhost \
--to=vinod.koul@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).