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


Groups > linux.kernel > #1270222

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

From Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Newsgroups linux.kernel
Subject Re: multi-codec support for arizona-ldo1 was Re: System with multiple arizona (wm5102) codecs
Date 2015-11-16 15:30 +0100
Message-ID <qvsX7-8rn-1@gated-at.bofh.it> (permalink)
References (5 earlier) <quuy1-3qR-65@gated-at.bofh.it> <quvu2-41A-1@gated-at.bofh.it> <quDKV-19N-11@gated-at.bofh.it> <quIhA-3Zt-7@gated-at.bofh.it> <quNhg-76F-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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/

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

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

csiph-web