linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] ARM: Tegra: Enable Harmony audio support
Date: Wed, 23 Feb 2011 13:51:43 -0800	[thread overview]
Message-ID: <AANLkTikmP5H6TQN1v1BNbGTfGokHgyXQ5LbFpEWgWjPB@mail.gmail.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF03112A5D95@HQMAIL01.nvidia.com>

On Wed, Feb 23, 2011 at 1:35 PM, Stephen Warren <swarren@nvidia.com> wrote:
> Olof Johansson wrote at Wednesday, February 23, 2011 2:25 PM:
>> On Wed, Feb 23, 2011 at 1:21 PM, Colin Cross <ccross@android.com> wrote:
>> > On Wed, Feb 23, 2011 at 1:08 PM, Olof Johansson <olof@lixom.net> wrote:
>> >> Stephen,
>> >>
>> >> Since this depends on i2c, and registers one of the adapters to do it,
>> >> we should just get the adapters registered separately (all of them)
>> >> before this. I was holding off that part of board code since the i2c
>> >> driver went up that maintainer path instead, but if Colin pulls it
>> >> into tegra for-next, then I'll go ahead with those peices as well.
>> >
>> > I'll merge the i2c-tegra branch into for-next (assuming Ben doesn't
>> > object to it), and you can put all the i2c devices in your pull
>> > request. ?That way we can get everything except this patch into the
>> > first pull request to Linus, and just put this patch into a second
>> > pull request once the ASoC branch is merged.
>>
>> Sure, that works. I'll stage the i2c changes tonight.
>
> OK, so just so I'm clear:
>
> Patches 1..4 are all going in as-is.
>
> I should re-post patch 5 once the merge window is open, having rebased
> it on Olof's i2c registration changes, and
> s/GPIO_WM8903/HARMONY_GPIO_WM8903/. Or, should I repost as soon as Olof
> has updated his branch with the I2C changes, and you'll just hold off
> applying it until the merge window?

How big would the delta be between a patch that would apply (and work)
with current .38-rc wm8903 platform data? If it's just the GPIO base,
we can merge everything but that and just do the small change late in
the merge window.

And yeah, please repost after the i2c stuff is in my branch, I'll
stage it accordingly.


-Olof

  reply	other threads:[~2011-02-23 21:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 18:58 [PATCH 0/5] ARM: Tegra: Harmony: Enable audio driver Stephen Warren
2011-02-23 18:58 ` [PATCH 1/5] ARM: Tegra: Add devices.c entries for audio Stephen Warren
2011-02-23 21:04   ` Colin Cross
2011-02-23 18:58 ` [PATCH 2/5] ARM: Tegra: Rename I2S clocks to match driver name Stephen Warren
2011-02-23 21:06   ` Colin Cross
2011-02-23 18:58 ` [PATCH 3/5] ARM: Tegra: Rename clk_dev1/2 to cdev1/2 Stephen Warren
2011-02-23 21:06   ` Colin Cross
2011-02-23 18:58 ` [PATCH 4/5] ARM: Tegra: Create defines for GPIO names Stephen Warren
2011-02-23 19:08   ` Colin Cross
2011-02-23 20:35     ` Stephen Warren
2011-02-23 20:39       ` Colin Cross
2011-02-23 20:49         ` Stephen Warren
2011-02-23 20:58           ` Colin Cross
2011-02-23 18:58 ` [PATCH 5/5] ARM: Tegra: Enable Harmony audio support Stephen Warren
2011-02-23 21:08   ` Colin Cross
2011-02-23 21:16     ` Stephen Warren
2011-02-23 21:19       ` Colin Cross
2011-02-23 21:08   ` Olof Johansson
2011-02-23 21:15     ` Colin Cross
2011-02-23 21:21       ` Olof Johansson
2011-02-23 21:22       ` Stephen Warren
2011-02-23 21:25         ` Olof Johansson
2011-02-23 21:21     ` Colin Cross
2011-02-23 21:24       ` Olof Johansson
2011-02-23 21:35         ` Stephen Warren
2011-02-23 21:51           ` Olof Johansson [this message]
2011-02-23 21:54             ` Stephen Warren
2011-02-23 22:48   ` Russell King - ARM Linux

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=AANLkTikmP5H6TQN1v1BNbGTfGokHgyXQ5LbFpEWgWjPB@mail.gmail.com \
    --to=olof@lixom.net \
    --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).