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>,
Rob Herring <robh@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: usb-dmac: Document SoC specific compatibility strings
Date: Thu, 10 Dec 2015 03:52:42 +0000 [thread overview]
Message-ID: <20151210035547.GL1854@localhost> (raw)
In-Reply-To: <1449035634-18761-1-git-send-email-horms+renesas@verge.net.au>
On Wed, Dec 02, 2015 at 02:53:54PM +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 compatibility 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 USB DMA Controller driver to follow this convention.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
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>,
Rob Herring <robh@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: usb-dmac: Document SoC specific compatibility strings
Date: Thu, 10 Dec 2015 09:25:48 +0530 [thread overview]
Message-ID: <20151210035547.GL1854@localhost> (raw)
In-Reply-To: <1449035634-18761-1-git-send-email-horms+renesas@verge.net.au>
On Wed, Dec 02, 2015 at 02:53:54PM +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 compatibility 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 USB DMA Controller driver to follow this convention.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2015-12-10 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 5:53 [PATCH v2] dmaengine: usb-dmac: Document SoC specific compatibility strings Simon Horman
2015-12-02 5:53 ` Simon Horman
2015-12-10 3:52 ` Vinod Koul [this message]
2015-12-10 3:55 ` 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=20151210035547.GL1854@localhost \
--to=vinod.koul@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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 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.