Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1269266 > unrolled thread

Re: multi-codec support for arizona-ldo1 was Re: System with multiple arizona (wm5102) codecs

Started byPavel Machek <pavel@ucw.cz>
First post2015-11-13 23:00 +0100
Last post2015-11-16 15:30 +0100
Articles 4 on this page of 24 — 5 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-13 23:00 +0100
    Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-14 00:00 +0100
      Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-14 08:50 +0100
        Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-14 13:40 +0100
          Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-14 19:00 +0100
            Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-14 20:00 +0100
              Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-14 22:20 +0100
                Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-15 01:20 +0100
                  Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-16 08:50 +0100
                    Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-16 12:00 +0100
                      Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-16 13:40 +0100
                        Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2015-11-16 15:20 +0100
                        Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2015-11-16 15:50 +0100
                        Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-16 18:40 +0100
                Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2015-11-16 15:30 +0100
                  Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-22 08:00 +0100
                    Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Lee Jones <lee.jones@linaro.org> - 2015-11-23 09:20 +0100
                      Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-23 11:20 +0100
                        Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Richard Fitzgerald <rf@opensource.wolfsonmicro.com> - 2015-11-23 11:30 +0100
                          Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Mark Brown <broonie@kernel.org> - 2015-11-23 12:40 +0100
                            Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2015-11-23 13:10 +0100
                              Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Lee Jones <lee.jones@linaro.org> - 2015-11-23 15:40 +0100
                              Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Pavel Machek <pavel@ucw.cz> - 2015-11-23 16:10 +0100
            Re: multi-codec support for arizona-ldo1 was Re: System with  multiple arizona (wm5102) codecs Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2015-11-16 15:30 +0100

Page 2 of 2 — ← Prev page 1 [2]


#1275269

FromCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
Date2015-11-23 13:10 +0100
Message-ID<qxY6u-1yt-7@gated-at.bofh.it>
In reply to#1275252
On Mon, Nov 23, 2015 at 11:30:41AM +0000, Mark Brown wrote:
> On Mon, Nov 23, 2015 at 10:25:22AM +0000, Richard Fitzgerald wrote:
> > On Mon, 2015-11-23 at 11:11 +0100, Pavel Machek wrote:
> 
> > > That's what I'm saying. It is good to know who is the person of
> > > authority, as you can't tell from the From: address.
> 
> > It's unreasonable to expect that one member of the Cirrus software team
> > has the time to answer every inquiry about our drivers and never goes on
> > vacation, or that there's only one person who is an authority about the
> > drivers. There's a mailing list for a reason.
> 
> It's perfectly OK to list multiple people - look at how other companies
> handle this, there's usually two or three people listed.

I don't really object to sticking a few people in here if the
general feeling is that would be better, but personally I didn't
see any problem with the current setup.

Shall I do a patch to add a few of us in here?

Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1275436

FromLee Jones <lee.jones@linaro.org>
Date2015-11-23 15:40 +0100
Message-ID<qy0rD-30z-1@gated-at.bofh.it>
In reply to#1275269
On Mon, 23 Nov 2015, Charles Keepax wrote:

> On Mon, Nov 23, 2015 at 11:30:41AM +0000, Mark Brown wrote:
> > On Mon, Nov 23, 2015 at 10:25:22AM +0000, Richard Fitzgerald wrote:
> > > On Mon, 2015-11-23 at 11:11 +0100, Pavel Machek wrote:
> > 
> > > > That's what I'm saying. It is good to know who is the person of
> > > > authority, as you can't tell from the From: address.
> > 
> > > It's unreasonable to expect that one member of the Cirrus software team
> > > has the time to answer every inquiry about our drivers and never goes on
> > > vacation, or that there's only one person who is an authority about the
> > > drivers. There's a mailing list for a reason.
> > 
> > It's perfectly OK to list multiple people - look at how other companies
> > handle this, there's usually two or three people listed.
> 
> I don't really object to sticking a few people in here if the
> general feeling is that would be better, but personally I didn't
> see any problem with the current setup.

Me either.

> Shall I do a patch to add a few of us in here?

Up to you.  Happy either way.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1275468

FromPavel Machek <pavel@ucw.cz>
Date2015-11-23 16:10 +0100
Message-ID<qy0UH-3v4-27@gated-at.bofh.it>
In reply to#1275269
On Mon 2015-11-23 11:46:37, Charles Keepax wrote:
> On Mon, Nov 23, 2015 at 11:30:41AM +0000, Mark Brown wrote:
> > On Mon, Nov 23, 2015 at 10:25:22AM +0000, Richard Fitzgerald wrote:
> > > On Mon, 2015-11-23 at 11:11 +0100, Pavel Machek wrote:
> > 
> > > > That's what I'm saying. It is good to know who is the person of
> > > > authority, as you can't tell from the From: address.
> > 
> > > It's unreasonable to expect that one member of the Cirrus software team
> > > has the time to answer every inquiry about our drivers and never goes on
> > > vacation, or that there's only one person who is an authority about the
> > > drivers. There's a mailing list for a reason.
> > 
> > It's perfectly OK to list multiple people - look at how other companies
> > handle this, there's usually two or three people listed.
> 
> I don't really object to sticking a few people in here if the
> general feeling is that would be better, but personally I didn't
> see any problem with the current setup.
> 
> Shall I do a patch to add a few of us in here?

Yes, please.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1270222

FromCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
Date2015-11-16 15:30 +0100
Message-ID<qvsX7-8rn-1@gated-at.bofh.it>
In reply to#1269513
On Sat, Nov 14, 2015 at 06:59:16PM +0100, Pavel Machek wrote:
> Hi!
> 
> > If you're asking about the regulator API or embedded ALSA both of those
> > are me but there are other things in here - the driver you're working
> > with and the MFD core at least.  At the minute I'm not convinced that
> > the problem here isn't just that the MFD and/or MFD core hasn't set up
> > the mappings to the child devices properly.
> 
> Ok, good. I don't understand how the things are expected to fit
> together. See above. I believe SND_SOC_ macros should have another
> argument "device", or maybe regulator names should have "device" name
> embedded in them.

Effectively the device is passed it is just implicit. If you look
where the regulator is actually registered in soc-dapm.c

	case snd_soc_dapm_regulator_supply:
		w->regulator = devm_regulator_get(dapm->dev, w->name);
		if (IS_ERR(w->regulator)) {

You see we are requesting the regulator with the dapm device,
which will correspond to the CODEC.

Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.kernel


csiph-web