Good news! Thanks for all the work.

> On Apr 21, 2016, at 23:41 , William Hermans <[email protected]> wrote:
> 
> Progress. I was able to get teh audio cape to load in 4.1.x.
> 
> william@beaglebone:~$ sudo sh -c "echo 'BB-BONE-AUDI-02' > 
> /sys/devices/platform/bone_capemgr/slots"
> [  104.123082] bone_capemgr bone_capemgr: part_number 'BB-BONE-AUDI-02', 
> version 'N/A'
> [  104.130898] bone_capemgr bone_capemgr: slot #4: override
> [  104.136277] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
> [  104.143283] bone_capemgr bone_capemgr: slot #4: 'Override Board 
> Name,00A0,Override Manuf,BB-BONE-AUDI-02'
> [  104.157826] bone_capemgr bone_capemgr: slot #4: dtbo 
> 'BB-BONE-AUDI-02-00A0.dtbo' loaded; overlay id #0
> [  104.311953] 2-0018 supply IOVDD not found, using dummy regulator
> [  104.318146] 2-0018 supply DVDD not found, using dummy regulator
> [  104.324235] 2-0018 supply AVDD not found, using dummy regulator
> [  104.330270] 2-0018 supply DRVDD not found, using dummy regulator
> [  104.339740] asoc-simple-card sound: tlv320aic3x-hifi <-> 48038000.mcasp 
> mapping ok
> 
> I used your device tree board file exactly Rick, with one modification.
> 
> #include "am33xx.dtsi"
> #include "am335x-bone-common.dtsi"
> 
> 
> The other two includes were removed. The rest of your source file is exactly 
> the same. But the am33xx-es2.dtsi include 
> file looked pretty much useless to me for this end goal. Looked like it had 
> mostly to do with voltage / processor frequency 
> scaling. Since I did not know if that was a 4.4.x specific feature, I just 
> removed the include. 
> 
> /*
>  * Device Tree Source for AM33XX SoC
>  *
>  * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
>  *
>  * This file is licensed under the terms of the GNU General Public License
>  * version 2.  This program is licensed "as is" without any warranty of any
>  * kind, whether express or implied.
>  */
> 
> / {
>       cpus {
>               cpu@0 {
>                       /*
>                        * To consider voltage drop between PMIC and SoC,
>                        * tolerance value is reduced to 2% from 4% and
>                        * voltage value is increased as a precaution.
>                        */
>                       operating-points = <
>                               /* kHz    uV */
>                               1000000 1325000
>                               800000  1300000
>                               600000  1112000
>                               300000  969000
>                       >;
>                       voltage-tolerance = <2>; /* 2 percentage */
> 
>                       clocks = <&dpll_mpu_ck>;
>                       clock-names = "cpu";
> 
>                       clock-latency = <300000>; /* From omap-cpufreq driver */
>               };
>       };
> };
> 
> On Thu, Apr 21, 2016 at 2:51 PM, Rick Mann <[email protected]> wrote:
> I don't have the BBB connected at the moment, but if I don't get you the 
> configuration by tonight, please feel free to email me again.
> 
> > On Apr 21, 2016, at 14:40 , Rafael Vega <[email protected]> wrote:
> >
> > I've made some progress but I still can't get any sound from the codec. I 
> > tried the two approaches suggested by Rick M earlier on this thread:
> >
> > 1) To use this dtb by Rick M and the audio cape overlay, and 2) to use this 
> > dtb (by RobertCNelson) with no overlay. In both cases I have the same 
> > apparent outcome: I can see I2C and I2S signals being driven by the BBB 
> > when I use aplay or speaker-test but I can't see any analog signal coming 
> > out of the codec.
> >
> > I have played around with alsamixer, I have deleted 
> > /var/lib/alsa/asound.state, used the one from here and no luck...
> >
> > I guess the next step would be to check the driver code and the codec 
> > datasheet to try to figure out what might be wrong. I found the code for 
> > the driver here (is that it?) but I have no experience in kernel-land 
> > development so I'm not sure what the compiling/debugging workflow would 
> > be...  My initial questions are:
> >
> > 1. How do you compile and install the driver/module without recompiling and 
> > installing the whole kernel?
> > 2. How does the driver code integrates with the device tree system? I can't 
> > see anyting in the driver code that suggests it's taking values or it's 
> > functions are being called from the dtb or the overlay.
> > 3. What is the simplest 'log' function callable from kernel land and where 
> > do I see the output?
> >
> > Any advice on  this would be appreciated!
> >
> > :)
> >
> > --
> > For more options, visit http://beagleboard.org/discuss
> > ---
> > You received this message because you are subscribed to the Google Groups 
> > "BeagleBoard" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to [email protected].
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/beagleboard/78d35232-c66d-49e8-841c-f77f99e5e368%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> 
> --
> Rick Mann
> [email protected]
> 
> 
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/5FD85278-8E85-486A-A0C7-62C6CB95D83F%40latencyzero.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CALHSORpyfyQ7K5SSOVj-Hx-zGWcZ6RozKx3QKtQG6nhFrDqMxQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
Rick Mann
[email protected]


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/388B2211-3BFC-486D-8A5A-F3F73DA8D391%40latencyzero.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to