On Apr 4, 2016 3:17 PM, "Rick Mann" <[email protected]> wrote: > > > > On Apr 4, 2016, at 06:57 , Robert Nelson <[email protected]> wrote: > > > > > > > > On Mon, Apr 4, 2016 at 8:41 AM, Robert Nelson <[email protected]> wrote: > > > > > > On Mon, Apr 4, 2016 at 4:47 AM, Rick Mann <[email protected]> wrote: > > 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 > > > > > > You need to add this to your base *.dtb: > > > > https://github.com/RobertCNelson/dtb-rebuilder/blob/4.1-ti/src/arm/am335x-boneblack-audio.dts#L17-L28 > > > > btw, the one thing i haven't tried, have everything in the clk defined except for the gpio and load that as part of the audio overlay.. > > > > side note, we just got audio (cape audio rev b) working a few weeks back, so this is relatively new > > Thanks, Robert. I'll give that a shot. I'm not immediately sure what my current base *.dtb is, nor how to build a new one and specify that be used. But maybe I can piggyback off the one you show there.
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, -- 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]. For more options, visit https://groups.google.com/d/optout.
