lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <B13DDD1D-479B-4B13-BB6B-ED103A59158A@holtmann.org>
Date:   Thu, 16 Feb 2017 17:22:42 +0100
From:   Marcel Holtmann <marcel@...tmann.org>
To:     Rajat Jain <rajatja@...gle.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        "Gustavo F. Padovan" <gustavo@...ovan.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Amitkumar Karwar <akarwar@...vell.com>,
        Wei-Ning Huang <wnhuang@...omium.org>,
        Xinming Hu <huxm@...vell.com>, netdev@...r.kernel.org,
        devicetree@...r.kernel.org, linux-bluetooth@...r.kernel.org,
        Brian Norris <briannorris@...gle.com>,
        linux-kernel@...r.kernel.org, rajatxjain@...il.com
Subject: Re: [PATCH v7 3/3] Bluetooth: btusb: Configure Marvell to use one of
 the pins for oob wakeup

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@...gle.com>
> Reviewed-by: Brian Norris <briannorris@...omium.org>
> Acked-by: Rob Herring <robh@...nel.org>
> ---
> 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ