Fundamental capemanager change between 4.1.x, and 4.4.x

Ok, so the following does NOT work on a 4.4.x kernel, but does on a 4.1.x kernel.

Starting off with 4.4.x kernel

william@beaglebone:~$ cat ti/WH-ADC-00A0.dts


/ {
compatible = “ti,beaglebone”, “ti,beaglebone-black”;

/* identification */
part-number = “WH-ADC”;
version = “00A0”;

fragment@0 {
target = <&tscadc>;
overlay {
compatible = “uio”;
uio-alias = “adc”;
status = “okay”;

william@beaglebone:~$ sudo touch /etc/modprobe.d/uio.conf
william@beaglebone:~$ sudo nano /etc/modprobe.d/uio.conf

put in /etc/modprobe.d/uio.conf

Just for added measure, yes the UIO driver does work . .

william@beaglebone:~$ lsuio
uio0: name=tscadc, version=devicetree, events=0
map[0]: addr=0x44E0D000, size=4096

It’s not the device tree node which is in the include am33xx.dtsi, they both seem to be exactly the same.

tscadc: tscadc@44e0d000 {
compatible = “ti,am3359-tscadc”;
reg = <0x44e0d000 0x1000>;
interrupt-parent = <&intc>;
interrupts = <16>;
ti,hwmods = “adc_tsc”;
status = “disabled”;

tsc {
compatible = “ti,am3359-tsc”;
am335x_adc: adc {
#io-channel-cells = <1>;
compatible = “ti,am3359-adc”;

Yeah, IDK, I’m beat for the night, but in my humble opinion, this is a show stopper. 4.4.x is not ready yet. Maybe tomorrow when better rested I’ll be able to think of something else to test. In hopes of getting this fixed / resolved.