lkml.org 
[lkml]   [2015]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: System with multiple arizona (wm5102) codecs
    On Tue, Sep 15, 2015 at 08:18:32AM +0200, Pavel Machek wrote:
    > Hi!
    >
    > > > I've got an embedded system with two arizona / wm5102 codecs.
    > > >
    > > > Unfortunately, kernel does not seem to be ready for that
    > > > configuration.
    > > >
    > > > In particular, drivers/regulator/arizona-ldo1.c and
    > > > drivers/regulator/arizona-micsupp.c register system-wide "MICVDD" and
    > > > "LDO1" regulators, but with two codecs in the system, we really have
    > > > wm5102-codec.1.MICVDD, wm5102-codec.2.MICVDD, wm5102-codec.1.LDO1 and
    > > > wm5102-codec.2.LDO1.
    > > >
    > > > That got me second codec working in two-codec configuration, but first
    > > > one still stops working as soon as two codecs are enabled.
    > > >
    > > > If you have idea what else needs fixing, let me know.
    > > >
    > > > Best regards,
    > > > Pavel
    > >
    > > I must confess I haven't ever tested a system with two Arizona
    > > CODECs connected. Yes it seems you would get clashes on the
    > > regulator names, I guess that would need to be fixed up. If you
    > > were doing so wm831x-ldo.c would probably make a reasonable
    > > example.
    > >
    > > I guess you would need to be careful with the machine driver as
    > > well, you will need to use a snd_soc_codec_conf structure for at
    > > least one (although I would do both) of the CODECs to give a
    > > prefix for all the widget/control names, otherwise those will
    > > clash and everything will probably behave very strangely. See
    > > sound/soc/samsung/bells.c for an example doing this for wm9081.
    > >
    > > Those are the only two things that spring to mind at the moment
    > > but keep me informed on how you are getting on and I will let you
    > > know if I can come up with any other traps.
    >
    > It seems that davinci-evm takes data from device tree, but then uses
    > statically-allocated evm_soc_card, which would lead to problems in
    > dual-codec config....?

    That somewhat depends on how you plan on doing things. I had
    assumed you would be having a single machine driver with both
    CODECs connected to it, in which case the statically allocated
    snd_soc_card wouldn't be a problem. However, if you wanted to
    have two seperate machine drivers with a single CODEC connected
    to each then you would have an issue.

    I guess either approach is reasonable and probably just depends
    on what your end goal is.

    Thanks,
    Charles


    \
     
     \ /
      Last update: 2015-09-15 11:01    [W:8.234 / U:0.224 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site