From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Sebastien Guiriec" <s-guiriec@ti.com>,
"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Benoît Cousson" <b-cousson@ti.com>,
"Jarkko Nikula" <jarkko.nikula@bitmer.com>,
linux-omap@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH V2 2/2] ASoC: OMAP2+: Move McBSP, DMIC and McPDM to generic DMA DT binding
Date: Mon, 11 Mar 2013 09:38:00 -0700 [thread overview]
Message-ID: <20130311163800.GK26093@atomide.com> (raw)
In-Reply-To: <20130311162814.GD10617@opensource.wolfsonmicro.com>
* Mark Brown <broonie@opensource.wolfsonmicro.com> [130311 09:32]:
> On Mon, Mar 11, 2013 at 09:27:00AM -0700, Tony Lindgren wrote:
>
> > I suggest you take the driver changes and Benoit takes the .dts
> > changes as those should be queued separately to avoid unnecessary
> > merge conflicts with the .dts files.
>
> Won't that cause a bisect issue if the driver starts looking for generic
> DT stuff that's not in the DTS files?
It should only affect additional features being enabled. When the .dts
changes get merged the new features just starts working. Or if the .dts
changes go in first, the driver starts working when the driver changes
go in.
If there's some dependency between the driver and the .dts changes
breaking booting etc, that should be fixed in the patches by
for example removing old legacy code later on in a separate series.
This allows us to break the dependency between arch/arm code and
drivers in most cases to keep things simpler.
Regards,
Tony
next prev parent reply other threads:[~2013-03-11 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 7:50 [PATCH V2 0/2] ASoC: OMAP2+: Update Audio IP with sDMA binding for DT boot Sebastien Guiriec
2013-03-11 7:50 ` [PATCH V2 1/2] ARM: dts: OMAP2+: Add SDMA Audio IPs bindings Sebastien Guiriec
2013-03-11 14:19 ` Peter Ujfalusi
2013-03-11 18:29 ` Jarkko Nikula
2013-03-11 7:50 ` [PATCH V2 2/2] ASoC: OMAP2+: Move McBSP, DMIC and McPDM to generic DMA DT binding Sebastien Guiriec
2013-03-11 14:18 ` Peter Ujfalusi
2013-03-11 18:29 ` Jarkko Nikula
2013-03-11 14:33 ` Mark Brown
2013-03-11 16:27 ` Tony Lindgren
2013-03-11 16:28 ` Mark Brown
2013-03-11 16:38 ` Tony Lindgren [this message]
2013-03-12 18:26 ` Mark Brown
2013-03-13 10:36 ` Mark Brown
2013-03-15 14:27 ` [PATCH V2 0/2] ASoC: OMAP2+: Update Audio IP with sDMA binding for DT boot Benoit Cousson
2013-03-15 16:56 ` Mark Brown
2013-03-15 17:01 ` Benoit Cousson
2013-03-15 17:05 ` Mark Brown
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=20130311163800.GK26093@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jarkko.nikula@bitmer.com \
--cc=lgirdwood@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=s-guiriec@ti.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).