/sys/class/leds/P8_10 is possible on the BBAI-64 or is it not possible?

I am using Linux to build a small bot of sorts. Many probably. But first…

/sys/class/leds/P8_10 is a location of a file that I need. Is this still part of the specification or do I need to pick and place DTS to handle such a task?

Seth

Update It

    P9_19_pinmux { pinctrl-0 = <&P9_19_i2c_pin>; };
    P9_20_pinmux { pinctrl-0 = <&P9_20_i2c_pin>; };
    P8_10_pinmux { pinctrl-0 = <&P8_10_gpio_pin>; };

This is what I am trying to convene on 6.1.x on the BBAI-64…

So far, I have nothing. Seriously. I must have missed something while things were changing.

I figured it would be as easy as:

#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/leds/common.h>

/dts-v1/;
/plugin/;

/*
 * Helper to show loaded overlays under: /proc/device-tree/chosen/overlays/
 */
&{/chosen} {
        overlays {
                SERVO-A2 = __TIMESTAMP__;
        };
};

&ocp {
    P9_19_pinmux { pinctrl-0 = <&P9_19_i2c_pin>; }; /* Why is pinctrl-0 set to -0? */
    P9_20_pinmux { pinctrl-0 = <&P9_20_i2c_pin>; };
    P8_10_pinmux { pinctrl-0 = <&P8_10_gpio_pin>; };
};

/* I think the muxing of the top three pins are done differently now */

&bone_i2c_2 {
    status = "okay";
    pca: pca@70 {
        compatible = "nxp,pca9685-pwm";
        #pwm-cells = <2>; /* Why does two cells exist for this one pwm? */
        reg = <0x70>;
        label = "servo";
        /* invert; */
        /* open-drain; */
    };
};

&bone_led_P8_10 {
    status = "okay";
    label = "borg";
    default-state = "off";
};

As you may be able to tell, I am trying to jump on board to write “my” first DTS script for a Cape.

And another update until I wait it out

#define J721E_IOPAD(pa, val, muxmode)
		(((pa) & 0x1fff)) ((val) | (muxmode))

What does the pa mean in the above #define property?