Hi Loic, I am okay with this DT patch for adding nxp,wakein-pin and nxp,wakeout-pin. Thanks, Neeraj > NXP bluetooth controller may have GPIO pins used and routed for `WAKE_IN` > and `WAKE_OUT`, such pin info must be known so that the driver is can > configure the controller's firmware accordingly. > > Signed-off-by: Loic Poulain <loic.poulain@xxxxxxxxxx> > --- > v2: No change > > .../bindings/net/bluetooth/nxp,88w8987-bt.yaml | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987- > bt.yaml b/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987- > bt.yaml > index 0a2d7baf5db3..04f55fac42ce 100644 > --- a/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987- > bt.yaml > +++ b/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987- > bt.yam > +++ l > @@ -40,6 +40,16 @@ properties: > Host-To-Chip power save mechanism is driven by this GPIO > connected to BT_WAKE_IN pin of the NXP chipset. > > + nxp,wakein-pin: > + $ref: /schemas/types.yaml#/definitions/uint8 > + description: > + The GPIO number of the NXP chipset used for BT_WAKE_IN. > + > + nxp,wakeout-pin: > + $ref: /schemas/types.yaml#/definitions/uint8 > + description: > + The GPIO number of the NXP chipset used for BT_WAKE_OUT. > + > required: > - compatible > > @@ -54,5 +64,7 @@ examples: > fw-init-baudrate = <3000000>; > firmware-name = "uartuart8987_bt_v0.bin"; > device-wakeup-gpios = <&gpio 11 GPIO_ACTIVE_HIGH>; > + nxp,wakein-pin = /bits/ 8 <18>; > + nxp,wakeout-pin = /bits/ 8 <19>; > }; > }; > -- > 2.34.1
