From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: nsekhar@ti.com, joelf@ti.com, linux@arm.linux.org.uk,
vinod.koul@intel.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
bcousson@baylibre.com
Subject: Re: [PATCH v2 4/5] ARM: dts: am33xx: Remove obsolete properties from edma node
Date: Wed, 14 May 2014 16:17:35 -0700 [thread overview]
Message-ID: <20140514231734.GC13427@atomide.com> (raw)
In-Reply-To: <1399977032-26469-5-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [140513 03:31]:
> dma-channels, ti,edma-regions and ti,edma-slots no longer needed in DT since
> the the same information is available in the IP's CCCFG register.
Sounds like this must go with the edma patches or else
applied later on. Probably best to merge it with edma:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2014-05-14 23:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 10:30 [PATCH v2 0/5] ARM/DT: edma: Get IP configuration from hardware Peter Ujfalusi
2014-05-13 10:30 ` [PATCH v2 1/5] ARM: edma: No need to clean the pdata in edma_of_parse_dt() Peter Ujfalusi
2014-05-13 10:30 ` [PATCH v2 2/5] ARM: edma: Get IP information from HW when booting with DT Peter Ujfalusi
2014-05-15 8:53 ` Sekhar Nori
2014-05-15 12:30 ` Peter Ujfalusi
2014-05-15 12:48 ` Sekhar Nori
2014-05-16 17:31 ` Joel Fernandes
2014-05-13 10:30 ` [PATCH v2 3/5] dt/bindings: ti,edma: Remove redundant properties from documentation Peter Ujfalusi
2014-05-15 8:01 ` Arnd Bergmann
2014-05-15 8:18 ` Peter Ujfalusi
2014-05-15 9:00 ` Sekhar Nori
2014-05-13 10:30 ` [PATCH v2 4/5] ARM: dts: am33xx: Remove obsolete properties from edma node Peter Ujfalusi
2014-05-14 23:17 ` Tony Lindgren [this message]
2014-05-13 10:30 ` [PATCH v2 5/5] ARM: dts: am4372: " Peter Ujfalusi
2014-05-14 23:18 ` Tony Lindgren
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=20140514231734.GC13427@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=joelf@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.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).