devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Rob Herring <rob.herring@calxeda.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <b-cousson@ti.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Russell King <linux@arm.linux.org.uk>,
	device-tree <devicetree-discuss@lists.ozlabs.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	Matt Porter <mporter@ti.com>, Felipe Balbi <balbi@ti.com>,
	Sourav Poddar <sourav.poddar@ti.com>,
	Balaji T K <balajitk@ti.com>
Subject: Re: [PATCH V2 0/2] ARM: dts: Add DT bindings for OMAP SDMA
Date: Fri, 8 Feb 2013 14:58:18 +0530	[thread overview]
Message-ID: <5114C532.1050506@ti.com> (raw)
In-Reply-To: <1360285506-22354-1-git-send-email-jon-hunter@ti.com>

On Friday 08 February 2013 06:35 AM, Jon Hunter wrote:
> Adds device-tree bindings from SDMA on OMAP2+ devices. DMA client
> bindings are also added for devices that have SPI and MMC bindings
> populated. Client binding data is based upon existing HWMOD data for
> OMAP and has been checked against OMAP documentation.
>
> Please note that the underlying (legacy) OMAP SDMA driver has not been
> ported over to DT and this still needs to be done. However, this allows
> DMA clients to look-up the DMA resource information via device-tree.
>
> Testing includes ...
> 1. Boot tested on OMAP3430 Beagle board, OMAP4430 Panda board and
>     OMAP4460 Panda board with and without device-tree present.
> 2. Testing of MMC1 with SD card on OMAP3430 Beagle board, OMAP4430
>     Panda board and OMAP4460 Panda board with and without device-tree
>     present.
>
> Testing branch available here [1].
>
> Series is based upon Tony Lindgren's omap-for-v3.9/multiplatform-v2
> branch [2] on top of the following ...
> - Vinod's topic/dmaengine_dt branch [3]
> - Matt Porter's series "DMA Engine support for AM33XX" [4]
> - Matt Porter's series "omap_hsmmc DT DMA Client support" [5]
> - Sourav Poddar's series "add omap mcspi device tree data" [6]
>
> V2 changes:
> - Updated to Tony's omap-for-v3.9/multiplatform-v2 branch to pull in
>    DMA changes for v3.9
> - Added comma to omap_dma_driver structure as pointed out by Arnd.
> - Updated OMAP SDMA DT binding compatible strings to indicate which
>    devices are bit compatible with each other with respect to the SDMA
>    controller. Grant had mentioned in the past that he wants the
>    compatible string to be based upon a particular device and not
>    something generic like "ti,omap-sdma".
>
> [1] https://github.com/jonhunter/linux/commits/dev-dt-dma
> [2] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git omap-for-v3.9/multiplatform-v2
> [3] http://git.infradead.org/users/vkoul/slave-dma.git/shortlog/refs/heads/topic/dmaengine_dt
> [4] http://permalink.gmane.org/gmane.linux.kernel.spi.devel/12508
> [5] http://permalink.gmane.org/gmane.linux.ports.arm.omap/93165
> [6] http://permalink.gmane.org/gmane.linux.kernel/1435002
>
> Jon Hunter (2):
>    ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
>    dmaengine: OMAP: Register SDMA controller with Device Tree DMA driver
>
>   .../devicetree/bindings/dma/omap-sdma.txt          |   51 ++++++++++++++++++++
>   arch/arm/boot/dts/omap2.dtsi                       |   12 +++++
>   arch/arm/boot/dts/omap3.dtsi                       |   40 +++++++++++++++
>   arch/arm/boot/dts/omap4.dtsi                       |   41 ++++++++++++++++
>   arch/arm/boot/dts/omap5.dtsi                       |   41 ++++++++++++++++
>   arch/arm/mach-omap2/dma.c                          |    4 ++
>   drivers/dma/omap-dma.c                             |   37 +++++++++++++-
>   7 files changed, 224 insertions(+), 2 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/dma/omap-sdma.txt
>
Acked-Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>

      parent reply	other threads:[~2013-02-08  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08  1:05 [PATCH V2 0/2] ARM: dts: Add DT bindings for OMAP SDMA Jon Hunter
2013-02-08  1:05 ` [PATCH V2 1/2] ARM: dts: OMAP2+: Add SDMA controller bindings and nodes Jon Hunter
2013-02-08  7:53   ` Felipe Balbi
     [not found] ` <1360285506-22354-1-git-send-email-jon-hunter-l0cyMroinI0@public.gmane.org>
2013-02-08  1:05   ` [PATCH V2 2/2] dmaengine: OMAP: Register SDMA controller with Device Tree DMA driver Jon Hunter
2013-02-08  7:55     ` Felipe Balbi
     [not found]       ` <20130208075552.GD21879-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-02-08 15:05         ` Jon Hunter
2013-02-08  9:28 ` Santosh Shilimkar [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=5114C532.1050506@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balajitk@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mporter@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=sourav.poddar@ti.com \
    --cc=tony@atomide.com \
    --cc=vinod.koul@intel.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).