From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: edma: Fix xbar mapping
Date: Tue, 29 Apr 2014 11:37:40 +0530 [thread overview]
Message-ID: <20140429060740.GM32284@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404282032150.6261@ionos.tec.linutronix.de>
On Mon, Apr 28, 2014 at 08:32:55PM +0200, Thomas Gleixner wrote:
> On Mon, 14 Apr 2014, Sekhar Nori wrote:
> > > Fix the issues by:
> > >
> > > - annotating the device tree entry with "/bits/ 16" as documented in
> > > the of_property_read_u16_array kernel doc
> > >
> > > - make the size of the xbar register mapping correct
> > >
> > > - invalidating the end of the array and not the start
> > >
> > > This convoluted mess wants to be completely rewritten as there is no
> > > point to keep the xbar_chan array memory and the iomapping of the xbar
> > > regs around forever. Marking the xbar mapped channels as used should
> > > be done right there.
> > >
> > > But that's a different issue and this patch is small enough to make it
> > > work and allows a simple backport for stable.
> > >
> > > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> >
> > This time, I tested this patch and FWIW you can add:
> >
> > Acked-by: Sekhar Nori <nsekhar@ti.com>
>
> Can someone pick this up please?
Shouldnt this go thru ARM tree?
--
~Vinod
next prev parent reply other threads:[~2014-04-29 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 20:48 [PATCH] arm: edma: Fix xbar mapping Thomas Gleixner
2014-04-14 14:14 ` Sekhar Nori
2014-04-28 18:32 ` Thomas Gleixner
2014-04-29 6:07 ` Vinod Koul [this message]
2014-04-29 6:40 ` Sekhar Nori
2014-05-11 5:16 ` Olof Johansson
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=20140429060740.GM32284@intel.com \
--to=vinod.koul@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).