Netdev List
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rajat Jain <rajatja@google.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Amitkumar Karwar <akarwar@marvell.com>,
	Wei-Ning Huang <wnhuang@chromium.org>,
	Xinming Hu <huxm@marvell.com>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-bluetooth@vger.kernel.org,
	Brian Norris <briannorris@google.com>,
	rajatxjain@gmail.com
Subject: Re: [PATCH 3/3] Bluetooth: btusb: Configure Marvel to use one of the pins for oob wakeup
Date: Mon, 19 Dec 2016 16:04:28 -0600	[thread overview]
Message-ID: <20161219220428.sn7pspjlss2w2rqb@rob-hp-laptop> (raw)
In-Reply-To: <1481742779-15105-3-git-send-email-rajatja@google.com>

On Wed, Dec 14, 2016 at 11:12:59AM -0800, Rajat Jain wrote:
> 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@google.com>
> ---
> Note that while I would have liked to name the compatible string as more
> like "marvell, usb8997-bt", the devicetrees/bindings/usb/usb-device.txt
> requires the compatible property to be of the form "usbVID,PID".
> 
>  .../{marvell-bt-sd8xxx.txt => marvell-bt-8xxx.txt} | 25 ++++++++-

Acked-by: Rob Herring <robh@kernel.org>

>  drivers/bluetooth/btusb.c                          | 59 ++++++++++++++++++++++
>  2 files changed, 82 insertions(+), 2 deletions(-)
>  rename Documentation/devicetree/bindings/net/{marvell-bt-sd8xxx.txt => marvell-bt-8xxx.txt} (76%)

      parent reply	other threads:[~2016-12-19 22:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 19:12 [PATCH 1/3] Bluetooth: btusb: Use an error label for error paths Rajat Jain
     [not found] ` <1481742779-15105-1-git-send-email-rajatja-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-12-14 19:12   ` [PATCH 2/3] Bluetooth: btusb: Add out-of-band wakeup support Rajat Jain
     [not found]     ` <1481742779-15105-2-git-send-email-rajatja-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-12-15  3:21       ` Brian Norris
     [not found]         ` <20161215032105.GA88921-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-12-16 19:43           ` Rajat Jain
2016-12-14 19:12   ` [PATCH 3/3] Bluetooth: btusb: Configure Marvel to use one of the pins for oob wakeup Rajat Jain
     [not found]     ` <1481742779-15105-3-git-send-email-rajatja-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-12-15  8:29       ` Gregory CLEMENT
2016-12-19 22:04     ` Rob Herring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161219220428.sn7pspjlss2w2rqb@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=akarwar@marvell.com \
    --cc=briannorris@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavo@padovan.org \
    --cc=huxm@marvell.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=rajatja@google.com \
    --cc=rajatxjain@gmail.com \
    --cc=wnhuang@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox