What is

GoogleGroups
1

I've got the current Debian/3.8 console build on an SD card, disabled HDMI in and out, but I'm still running into some issue trying to load my overlay. I'm not sure what's going on, exactly. My DTS (https://github.com/JetForMe/podtique/blob/v1/bbb/cape/Podtique1/BB-ENABLE-PRU.dts).

[ 165.659756] bone-capemgr bone_capemgr.9: part_number 'BB-ENABLE-PRU', version 'N/A'
[ 165.659841] bone-capemgr bone_capemgr.9: slot #7: generic override
[ 165.659858] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 7
[ 165.659875] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,BB-ENABLE-PRU'
[ 165.659963] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'BB-ENABLE-PRU-00A0.dtbo
[ 165.659979] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'BB-ENABLE-PRU-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[ 165.663169] bone-capemgr bone_capemgr.9: slot #7: dtbo 'BB-ENABLE-PRU-00A0.dtbo' loaded; converting to live tree
[ 165.663554] bone-capemgr bone_capemgr.9: slot #7: #6 overlays
[ 165.669165] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe
[ 165.669204] platform gpio_helper.11: Driver gpio-of-helper requests probe deferral
[ 165.683866] pinctrl-single 44e10800.pinmux: pin 44e10850 already requested by rstctl.4; cannot claim for 48038000.mcasp
[ 165.695265] pinctrl-single 44e10800.pinmux: pin-20 (48038000.mcasp) status -22
[ 165.702841] pinctrl-single 44e10800.pinmux: could not request pin 20 on device pinctrl-single
[ 165.723660] davinci-mcasp 48038000.mcasp: pins are not configured from the driver
[ 165.723999] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe
[ 165.724029] platform gpio_helper.11: Driver gpio-of-helper requests probe deferral
[ 165.725584] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe
[ 165.725615] platform gpio_helper.11: Driver gpio-of-helper requests probe deferral
[ 165.726787] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe
[ 165.726816] platform gpio_helper.11: Driver gpio-of-helper requests probe deferral
[ 165.742052] omap_hwmod: pruss: failed to hardreset
[ 165.759241] bone-capemgr bone_capemgr.9: slot #7: Applied #6 overlays.
[ 165.786484] pruss_uio 4a300000.pruss: pins are not configured from the driver
[ 165.794415] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe
[ 165.794452] platform gpio_helper.11: Driver gpio-of-helper requests probe deferral

2

[ 165.683866] pinctrl-single 44e10800.pinmux: pin 44e10850 already requested by rstctl.4; cannot claim for 48038000.mcasp

^ ^

3

[ 165.683866] pinctrl-single 44e10800.pinmux: pin 44e10850 already requested by rstctl.4; cannot claim for 48038000.mcasp

^ ^

Yeah, I saw that, but that's part of my question. What is that? I don't get that on 4.x kernels. I also don't know what this means:

[ 165.723999] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe

In any case, it's a bit moot now. I managed to get the audio cape working with its dtbo on 3.8 kernel. Onward...

4

Yeah, I saw that, but that’s part of my question. What is that? I don’t get that on 4.x kernels. I also don’t know what this means:

*> [ 165.723999] gpio-of-helper gpio_helper.11: could not find pctldev for node /ocp/interrupt-controller@*48200000, deferring probe

In any case, it’s a bit moot now. I managed to get the audio cape working with its dtbo on 3.8 kernel. Onward…

The bit I copy / pasted back to you I would assume is related to reset. The part you pasted back to me, I honestly haven’t a clue either. But was going to suggest that you recompile your dtb’s for your current kernel. Perhaps not related, but it’s the only thing I could think of.

Grats on getting your cape configured !!!

5

Sadly, I haven't done this yet. I got the CircuitCo Audio Cape working with 3.8 kernel. Nothing more. Found some discrepancies in my DTS, but fixing those have changed nothing.