If the platform provides it, use the reset gpio to reset the BT
chip (requested by the HCI core if needed). This has been found helpful
on some of Intel bluetooth controllers where the firmware gets stuck and
the only way out is a hard reset pin provided by the platform.
Signed-off-by: Rajat Jain
If the platform provides it, use the reset gpio to reset the BT
chip (requested by the HCI core if needed). This has been found helpful
on some of Intel bluetooth controllers where the firmware gets stuck and
the only way out is a hard reset pin provided by the platform.
Signed-off-by: Rajat Jain
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
. The
compatible string is in compliance with
Documentation/devicetree/bindings/usb/usb-device.txt
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
Acked-by: Rob Herring <r...@kernel.org>
---
v7: Change the BTUSB_OOB_
Use a label to remove the repetetive cleanup, for error cases.
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v7: same as v6
v6: same as v5
v5: same as v4
v4: same as v3
v3: Added Brian's "Reviewed-by"
v2: same as
Use a label to remove the repetetive cleanup, for error cases.
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v6: same as v5
v5: same as v4
v4: same as v3
v3: Added Brian's "Reviewed-by"
v2: same as v1
drivers/
. The
compatible string is in compliance with
Documentation/devicetree/bindings/usb/usb-device.txt
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
Acked-by: Rob Herring <r...@kernel.org>
---
v6: Remove the newlines in error statemen
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
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
. The
compatible string is in compliance with
Documentation/devicetree/bindings/usb/usb-device.txt
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
Acked-by: Rob Herring <r...@kernel.org>
---
v5: Move the call to pm_wakeup_event() to t
Use a label to remove the repetetive cleanup, for error cases.
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v5: same as v4
v4: same as v3
v3: Added Brian's "Reviewed-by"
v2: same as v1
drivers/
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
Use a label to remove the repetetive cleanup, for error cases.
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v4: same as v3
v3: Added Brian's "Reviewed-by"
v2: same as v1
drivers/bluetooth/btusb.c | 19 +
. The
compatible string is in compliance with
Documentation/devicetree/bindings/usb/usb-device.txt
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v4: Move the set_bit(BTUSB_OOB_WAKE_DISABLED,..) call to the beginning of
btusb_con
Use a label to remove the repetetive cleanup, for error cases.
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v3: Added Brian's "Reviewed-by"
v2: same as v1
drivers/bluetooth/btusb.c | 19 +--
1 file
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
. The
compatible string is in compliance with
Documentation/devicetree/bindings/usb/usb-device.txt
Signed-off-by: Rajat Jain <raja...@google.com>
Reviewed-by: Brian Norris <briannor...@chromium.org>
---
v3: Add Brian's "Reviewed-by"
v2: * Use interrupt-names ("wakeup") ins
Hi Brian,
On Mon, Dec 19, 2016 at 3:10 PM, Brian Norris <briannor...@chromium.org> wrote:
> Hi Rajat,
>
> On Fri, Dec 16, 2016 at 11:30:03AM -0800, Rajat Jain wrote:
>> Some onboard BT chips (e.g. Marvell 8997) contain a wakeup pin that
>> can be connected to a gp
Hi Brian,
I've just posted a v2 patchset after taking care of your your
comments. Please see inline below.
On Wed, Dec 14, 2016 at 7:21 PM, Brian Norris <briannor...@chromium.org> wrote:
> Hi,
>
> On Wed, Dec 14, 2016 at 11:12:58AM -0800, Rajat Jain wrote:
>> Some BT chi
. The
compatible string is in compliance with
Documentation/devicetree/bindings/usb/usb-device.txt
Signed-off-by: Rajat Jain <raja...@google.com>
---
v2: * Use interrupt-names ("wakeup") instead of assuming first interrupt.
* Leave it on device tree to specify IRQ flags (level /edge trigg
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
Use a label to remove the repetetive cleanup, for error cases.
Signed-off-by: Rajat Jain <raja...@google.com>
---
v2: same as v1
drivers/bluetooth/btusb.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/blu
-by: Rajat Jain <raja...@google.com>
---
Documentation/devicetree/bindings/net/btusb.txt | 38
drivers/bluetooth/btusb.c | 82 +
2 files changed, 120 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/btusb.txt
diff
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
Use a label to remove the repetetive cleanup, for error cases.
(This label will also be used in subsequent patches).
Signed-off-by: Rajat Jain <raja...@google.com>
---
drivers/bluetooth/btusb.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/d
.
The function mwifiex_probe_of()nodetself is currently only a place
holder with the next patch adding content to it.
Signed-off-by: Rajat Jain <raja...@google.com>
---
drivers/net/wireless/marvell/mwifiex/main.c| 15 ++-
drivers/net/wireless/marvell/mwifiex/main.h| 2 +-
d
ion if needed.
This is needed for subsequent patches in this patchset that
intend to unify and consolidate some of the code that would
otherwise have to be duplicated among the interface drivers
(sdio, pcie, usb).
Signed-off-by: Rajat Jain <raja...@google.com>
---
drivers/net/wireless/marvel
Commit ce4f6f0c353b ("mwifiex: add platform specific wakeup interrupt
support") added WoWLAN feature only for sdio. This patch moves that
code to the common module so that all the interface drivers can use
it for free. It enables pcie and sdio for its use currently.
Signed-off-by:
2 patches applied:
https://patchwork.kernel.org/patch/9362275/
https://patchwork.kernel.org/patch/9390225/
Rajat Jain (3):
mwifiex: Allow mwifiex early access to device structure
mwifiex: Introduce mwifiex_probe_of() to parse common properties
mwifiex: Enable WoWLAN for both sdio and pcie
driv
as the system was
apparently confused about the wakeup source.
Signed-off-by: Wei-Ning Huang <wnhu...@google.com>
Signed-off-by: Rajat Jain <raja...@google.com>
Tested-by: Wei-Ning Huang <wnhu...@chromium.org>
Reviewed-by: Eric Caruso <ejcar...@chromium.org>
Acked-by
Hello Kalie,
On Mon, Oct 3, 2016 at 6:04 AM, Kalle Valo <kv...@codeaurora.org> wrote:
> Rajat Jain <raja...@google.com> wrote:
>> Enable notifying wakeup source to the PM core in case of
>> a wake on wireless LAN event.
>>
>> Signed-off-by: Wei-Ning H
Enable notifying wakeup source to the PM core. This allow darkresume to
correctly track wakeup source and mark mwifiex_plt as 'automatic' wakeup
source.
Signed-off-by: Wei-Ning Huang <wnhu...@google.com>
Signed-off-by: Rajat Jain <raja...@google.com>
Tested-by: Wei-Ning
Enable notifying wakeup source to the PM core in case of
a wake on wireless LAN event.
Signed-off-by: Wei-Ning Huang <wnhu...@google.com>
Signed-off-by: Rajat Jain <raja...@google.com>
Tested-by: Wei-Ning Huang <wnhu...@chromium.org>
Reviewed-by: Eric Caruso <ejcar...@chro
Please ignore, not sure why this landed without a subject.
On Tue, Sep 27, 2016 at 9:50 AM, Rajat Jain <raja...@google.com> wrote:
> From: Wei-Ning Huang <wnhu...@google.com>
>
> Date: Thu, 17 Mar 2016 11:43:16 +0800
> Subject: [PATCH] mwifiex: report wakeup for wowlan
>
ed-off-by: Wei-Ning Huang <wnhu...@google.com>
Signed-off-by: Rajat Jain <raja...@google.com>
Tested-by: Wei-Ning Huang <wnhu...@chromium.org>
Reviewed-by: Eric Caruso <ejcar...@chromium.org>
---
drivers/net/wireless/marvell/mwifiex/sdio.c | 8
drivers/net/wireless/m
Enable notifying wakeup source to the PM core. This allow darkresume to
correctly track wakeup source and mark mwifiex_plt as 'automatic' wakeup
source.
Signed-off-by: Wei-Ning Huang <wnhu...@google.com>
Signed-off-by: Rajat Jain <raja...@google.com>
Tested-by: Wei-Ning
36 matches
Mail list logo
