Switch to r7, just pushed it out this morning.
dtb=am335x-boneblack-audio.dtb
>
> Out of curiosity, why can't this be done as an overlay (to help me understand the Device Tree better)?
>
Just a bug in the clock driver, the dynamic overlay changes is still very fragile. In most cases moving the driver as a module vs built-in, fixes it right up.. Except this is the clock driver, it needs to be built in..
Regards,
I see that on 4.1.14-bone-rt-r17 kernel the edma fix is compiled into
the am335x-boneblack-emmc-overlay.dtb resulting in
any audio cape overlay not loading.
so i guess i can grab this file
https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-emmc-overlay.dts
but i have no idea how to complie it and what paths i need to include to
get it to complie
I am wondering why that *fix* was needed and why it wants to enable the
davinci_mdio_default pins so we cant enable audio overlays
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhoexceTQ%2B69QvjqTazHkwdy%2BmtUpYYBQctFqsPGgNjew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5717F175.6030608%40gmail.com.
Keep in mind I'm on 4.4.7-bone-rt-r9, not 4.1.x. Dunno if that matters.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/2CEFA005-1914-4280-8FB5-5424A2F73517%40latencyzero.com.
Keep in mind I'm on 4.4.7-bone-rt-r9, not 4.1.x. Dunno if that matters.
We're trying to determine that here. Were you able to get the audio cape loaded at all with a 4.1.x kernel ? We really do not want to move outside of a "stable" kernel if at all possible.
4.4.x is also an lts, the overlay patches between v4.1.x and v4.4.x are almost identical..getting really close to swap v4.1.x-ti for v4.4.x-ti... ;)Regards,
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYj6e5fESiEp9-%2BW3X_y9Uex9tf2fT2mqJbq%2B%3DAVR4oteQ%40mail.gmail.com.
4.4.x is also an lts, the overlay patches between v4.1.x and v4.4.x are almost identical..getting really close to swap v4.1.x-ti for v4.4.x-ti... ;)Regards,Ok, so we're not sticking to the traditional even / odd minor version number meanings ?
Version | Maintainer | Released | Projected EOL |
---|---|---|---|
4.4 | Greg Kroah-Hartman | 2016-01-10 | Feb, 2018 |
4.1 | Sasha Levin | 2015-06-21 | Sep, 2017 |
3.18 | Sasha Levin | 2014-12-07 | Jan, 2017 |
3.14 | Greg Kroah-Hartman | 2014-03-30 | Aug, 2016 |
3.12 | Jiri Slaby | 2013-11-03 | Jan, 2017 |
3.10 | Willy Tarreau | 2013-06-30 | Oct, 2017 |
3.4 | Li Zefan | 2012-05-20 | Sep, 2016 |
3.2 | Ben Hutchings | 2012-01-04 | May, 2018 |
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYgWuJQFTrw3w1Xuk7jYY0jmnp9ZC1pRkXBgortFGttjjA%40mail.gmail.com.
Ok, still not working.Robert, so is there anything note worthy not working in 4.4* ? We have to know up front . . .
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYguxbq458W85EPd%3DzGKDsJ%3D9_9tNfPn%3Db-PXBhmgrAGqw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/69CB4EB2-08F0-454E-BBC6-5D51C4467098%40latencyzero.com.
So much i dont know.
rick or robert where might i get this file ?
am33xx-es2.dtsi
Its not in the dts-rebuilder i installed and Ricks new dts file seems to
require it to compile
src/arm/am335x-boneblack-audio-emmc.dts:11:27: fatal error:
am33xx-es2.dtsi: No such file or directory
Designing hardware is so much more easier :P
I remember firmware in the old days patch the code and burn some
bipolar proms install and continue
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYgRwax_s-irGPEzmJiDxhs_5QDA6cNJpTJ1dBpOgAPzRw%40mail.gmail.com.
move all the remaining entries that are in the overlay into a new .dts file based on this <
http://pastebin.com/Wja7ZQRk>, compile that, and load it at boot.
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5ecc19c3-9936-4fea-a87f-8564fab9d9ed%40googlegroups.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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiVST5W%3DXxUFAYjx7oqK64MDPqiKfijadYibztjVRCTPg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/B16BFBCC-2FC3-458E-98FB-D4D7AAA490B8%40latencyzero.com.
Are you able to make it work with my original .dtb and loading the BB-BONE-AUDI-02 overlay via capemgr?
Yeah, that's the file that's working for me, EXCEPT: I modified my am33xx-overlay-edma-fix.dtsi to comment out the two mcasp entries. If I boot with that (on 4.4.7-bone-rt-r9), then I can load the BB-BONE-AUDI-02 overlay, and then I can use aplay and speaker-test.
At this point, though, the channels are not quite right. Only the left works. This is hopefully due to a very badly configured ALSA.
BTW, your buddy surely didn't use my cape; I've only built one, and it's here. :-) The last few days I've been using the CircuitCo AudioCape Rev B (the Rev A has a different codec). My cape is almost identical to the Rev B, so I'll soon try it again.
--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/50d483c1-29a2-4305-81af-cc5145720d76%40googlegroups.com.
#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 */
};
};
};
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5FD85278-8E85-486A-A0C7-62C6CB95D83F%40latencyzero.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/388B2211-3BFC-486D-8A5A-F3F73DA8D391%40latencyzero.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrJnsVu_c1KuKF3xpRyiQF%3D8QXe%2BCuA0fHDkN0FKACx9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
I'm trying to get my audio cape to work (which is nearly identical to the cape that was available for sale). I've had it working to some level of success with past kernels (3.1.18), but now I'm on 4.4.6. My existing DTS didn't work, so I'm looking at how the BB-BONE-AUDI-02 DTS is written.
One of the differences is that it doesn't explicitly call out the McASP clock frequency like the older one did. Instead, it seems to refer to clk_mcasp0. But when I copy the same code into my DTS, I get:
[ 103.180866] of_resolve_phandles: Could not find symbol 'clk_mcasp0'
[ 103.187269] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree
I found it defined by grepping /boot/dtbs. It's in /boot/dtbs/4.4.6-bone-rt-r6/am335x-abbbi.dtb. Where can I find the source files for these DTBs?
Is this dtb part of what's loaded by default in 4.4.6-bone-rt-r6? If not, can I copy the definition into my
FWIW, here's my DTS and some output from dmesg: http://pastebin.com/niDkWdWV
Thanks,
--
Rick Mann
rm...@latencyzero.com