All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Eduardo Valentin <eduardo.valentin@nokia.com>
Cc: alsa-devel@alsa-project.org, ext Tony Lindgren <tony@atomide.com>,
	"Ujfalusi Peter (Nokia-D/Tampere)" <peter.ujfalusi@nokia.com>,
	"Nurkkala Eero.An (EXT-Offcode/Oulu)"
	<ext-Eero.Nurkkala@nokia.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	ALSA-Devel <alsa-devel@vger.kernel.org>
Subject: Re: [PATCH 5/8] board-rx51-peripherals: split vaux3 and vmmc2 supplies
Date: Fri, 9 Oct 2009 12:03:47 +0100	[thread overview]
Message-ID: <20091009110346.GC5082@sirena.org.uk> (raw)
In-Reply-To: <20091009064529.GD6616@esdhcp037198.research.nokia.com>

On Fri, Oct 09, 2009 at 09:45:29AM +0300, Eduardo Valentin wrote:
> On Thu, Oct 08, 2009 at 03:21:10PM +0200, Mark Brown wrote:
> > On Thu, Oct 08, 2009 at 02:58:54PM +0300, Eduardo Valentin wrote:

> > I may have missed it but I don't see rx51_vmmc2_supply added back
> > anywhere in the patch?

> yes. That's because this patch is just to split then. As you can see
> in current code, this structure, rx51_vmmc2_supply, is actually used
> by rx51_vaux3_mmc and rx51_vmmc2. So the idea is to have separated
> supplies for each one. This patch just splits then. Patch 0006 of this
> series adds usage of rx51_vmmc2_supply.

Might be an idea to change the description to something like "add a
separate structure for...", it wasn't 100% clear what was going on
(probably because the diff doesn't include sufficient context to make it
clear).

> > ...using dev_name rather than dev should avoid the need to do this at
> > runtime.

> I see your point. As mentioned above, this patch is just a split.
> I just added rx51_vaux3_supply to be owned by rx51_vaux3_mmc. And
> let the code behavior as it was before.

> Maybe your proposal must be sent into a separated patch/patch series (?).

Yes, it's definately a separate patch - might be good to put it into the
series before this one.

  reply	other threads:[~2009-10-09 11:03 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 11:58 [PATCH 0/8] RX-51 audio drivers Eduardo Valentin
2009-10-08 11:58 ` [PATCH 1/8] ASoC: TPA6130A2 amplifier driver Eduardo Valentin
2009-10-08 12:30   ` Eero Nurkkala
2009-10-08 12:30   ` Eero Nurkkala
2009-10-08 13:07     ` Peter Ujfalusi
2009-10-08 13:07     ` Peter Ujfalusi
2009-10-08 12:52   ` Mark Brown
2009-10-08 12:52   ` Mark Brown
2009-10-08 13:38     ` Peter Ujfalusi
2009-10-08 13:53       ` Mark Brown
2009-10-09  6:53         ` Peter Ujfalusi
2009-10-09  6:53         ` Peter Ujfalusi
2009-10-09 10:36           ` Mark Brown
2009-10-08 13:53       ` Mark Brown
2009-10-08 13:38     ` Peter Ujfalusi
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 11:58 ` [PATCH 2/8] ASoC: OMAP: RX-51 Machine driver and AIC34b_dummy driver Eduardo Valentin
2009-10-08 12:31   ` Eero Nurkkala
2009-10-08 13:18     ` Eduardo Valentin
2009-10-08 13:18     ` Eduardo Valentin
2009-10-08 12:31   ` Eero Nurkkala
2009-10-08 13:11   ` Mark Brown
2009-10-09  5:44     ` Jarkko Nikula
2009-10-09  5:44     ` Jarkko Nikula
2009-10-09  6:37       ` Eduardo Valentin
2009-10-09 12:19         ` Mark Brown
2009-10-09  6:37       ` Eduardo Valentin
2009-10-08 13:11   ` Mark Brown
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 11:58 ` [PATCH 3/8] McBSP: OMAP3: Add Sidetone feature Eduardo Valentin
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 13:17   ` Mark Brown
2009-10-08 13:17   ` Mark Brown
2009-10-08 13:23     ` Eduardo Valentin
2009-10-08 13:27       ` Mark Brown
2009-10-09  5:09     ` Eero Nurkkala
2009-10-09 10:44       ` [alsa-devel] " Mark Brown
2009-10-12  6:17         ` Eero Nurkkala
2009-10-12  9:12           ` Mark Brown
2009-10-12  9:28             ` Eero Nurkkala
2009-10-12  9:32               ` Mark Brown
2009-10-12 10:28                 ` Eero Nurkkala
2009-10-12 10:33                   ` Mark Brown
2009-10-08 11:58 ` [PATCH 4/8] OMAP: RX51: Add audio board file Eduardo Valentin
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 11:58 ` [PATCH 5/8] board-rx51-peripherals: split vaux3 and vmmc2 supplies Eduardo Valentin
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 13:21   ` Mark Brown
2009-10-08 13:21   ` Mark Brown
2009-10-09  6:45     ` Eduardo Valentin
2009-10-09  6:45     ` Eduardo Valentin
2009-10-09 11:03       ` Mark Brown [this message]
2009-10-12  8:08         ` Eduardo Valentin
2009-10-12  9:18           ` Mark Brown
2009-10-14 17:15             ` Tony Lindgren
2009-10-15  9:01               ` Mark Brown
2009-10-16 16:14                 ` Tony Lindgren
2009-10-08 11:58 ` [PATCH 6/8] RX-51: Audio: Add usage of regulator framework to control VMMC2 Eduardo Valentin
2009-10-08 13:26   ` Mark Brown
2009-10-12  9:04     ` Eduardo Valentin
2009-10-12  9:21       ` Mark Brown
2009-10-19  9:13         ` Eduardo Valentin
2009-10-19  9:13         ` Eduardo Valentin
2009-10-19  9:23           ` Mark Brown
2009-10-19  9:24             ` Mark Brown
2009-10-19  9:24             ` Mark Brown
2009-10-19  9:23           ` Mark Brown
2009-10-12  9:21       ` Mark Brown
2009-10-12  9:04     ` Eduardo Valentin
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 11:58 ` [PATCH 7/8] ASoC: tlv320aic3x: add initial usage of regulator framework to control avdd_dac Eduardo Valentin
2009-10-08 11:58 ` Eduardo Valentin
2009-10-08 12:17   ` Eero Nurkkala
2009-10-08 12:17   ` Eero Nurkkala
2009-10-08 13:17     ` Eduardo Valentin
2009-10-08 13:40     ` Mark Brown
2009-10-08 13:40     ` Mark Brown
2009-10-08 15:44       ` ext-Eero.Nurkkala
2009-10-08 15:44       ` ext-Eero.Nurkkala
2009-10-08 16:01         ` Mark Brown
2009-10-09  4:28           ` Eero Nurkkala
2009-10-09 10:19             ` Mark Brown
2009-10-09 10:19             ` Mark Brown
2009-10-09  4:28           ` Eero Nurkkala
2009-10-08 16:01         ` Mark Brown
2009-10-08 13:38   ` Mark Brown
2009-10-08 13:38   ` Mark Brown
2009-10-08 11:58 ` [PATCH 8/8] ASoC: tpa6130a2: Control vdd using regulator framework Eduardo Valentin
2009-10-08 13:43   ` Mark Brown
2009-10-08 13:56     ` Eduardo Valentin
2009-10-08 14:41       ` Mark Brown
2009-10-08 14:41       ` Mark Brown
2009-10-08 11:58 ` Eduardo Valentin

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=20091009110346.GC5082@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-devel@vger.kernel.org \
    --cc=eduardo.valentin@nokia.com \
    --cc=ext-Eero.Nurkkala@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@nokia.com \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.