linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci McASP changes for v4.1
Date: Thu, 19 Mar 2015 13:22:11 +0530	[thread overview]
Message-ID: <550A802B.7050201@ti.com> (raw)

The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:

  Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v4.1/mcasp

for you to fetch changes up to 6cfdf55b7746a3b1bc324a9e64abe2f055368e6f:

  ARM: davinci: dm646x: Add interrupt resource for McASPs (2015-03-18 17:19:50 +0530)

----------------------------------------------------------------
This pull request contains cleanups and
non-urgent fixes for DaVinci McASP platform
support code.

----------------------------------------------------------------
Peter Ujfalusi (7):
      ARM: davinci: devices-da8xx: Add resource name for the McASP DMA request
      ARM: davinci: devices-da8xx: Add interrupt resource to McASP structs
      ARM: davinci: devices-da8xx: Clean up and correct the McASP device creation
      ARM: davinci: devices-da8xx: Add support for McASP2 on da830
      ARM: davinci: dm646x: Clean up the McASP DMA resources
      ARM: davinci: irqs: Correct McASP1 TX interrupt definition for DM646x
      ARM: davinci: dm646x: Add interrupt resource for McASPs

 arch/arm/mach-davinci/asp.h               |    7 +++
 arch/arm/mach-davinci/devices-da8xx.c     |   80 ++++++++++++++++++++++++++---
 arch/arm/mach-davinci/dm646x.c            |   24 ++++++---
 arch/arm/mach-davinci/include/mach/irqs.h |    2 +-
 4 files changed, 98 insertions(+), 15 deletions(-)

             reply	other threads:[~2015-03-19  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  7:52 Sekhar Nori [this message]
2015-03-31 11:57 ` [GIT PULL] DaVinci McASP changes for v4.1 Sekhar Nori
2015-04-02  0:57 ` 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=550A802B.7050201@ti.com \
    --to=nsekhar@ti.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).