Hi,
> The Marvell devices may have many gpio pins, and hence for wakeup
> on these out-of-band pins, the chip needs to be told which pin is
> to be used for wakeup, using an hci command.
>
> Thus, we read the pin number etc from the device tree node and send
> a command to the chip.
>
> Signed-off-by: Rajat Jain <rajatja@xxxxxxxxxx>
> Reviewed-by: Brian Norris <briannorris@xxxxxxxxxxxx>
> Acked-by: Rob Herring <robh@xxxxxxxxxx>
> ---
> v7: Same as v6
> v6: same as v5
> v5: same as v5
> v4: same as v3
> v3: * remove the Marvell specific id table and check
> * Add reference to marvell-bt-8xxx.txt in btusb.txt
> * Add "Reviewed-by" and "Acked-by"
> v2: Fix the binding document to specify to use "wakeup" interrupt-name
>
> Documentation/devicetree/bindings/net/btusb.txt | 3 ++
> .../{marvell-bt-sd8xxx.txt => marvell-bt-8xxx.txt} | 46 +++++++++++++++----
> drivers/bluetooth/btusb.c | 51 ++++++++++++++++++++++
> 3 files changed, 92 insertions(+), 8 deletions(-)
> rename Documentation/devicetree/bindings/net/{marvell-bt-sd8xxx.txt => marvell-bt-8xxx.txt} (50%)
all 3 patches have been applied to bluetooth-next tree.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
