From: Matthias Kaehlcke <mka@chromium•org>
To: Brian Norris <briannorris@chromium•org>
Cc: devicetree@vger•kernel.org, Heiko Stuebner <heiko@sntech•de>,
linux-bluetooth@vger•kernel.org,
Marcel Holtmann <marcel@holtmann•org>,
Douglas Anderson <dianders@chromium•org>,
linux-kernel@vger•kernel.org, linux-rockchip@lists•infradead.org,
Rob Herring <robh+dt@kernel•org>,
Enric Balletbo i Serra <enric.balletbo@collabora•com>,
Rajat Jain <rajatja@google•com>,
linux-arm-kernel@lists•infradead.org,
Johan Hedberg <johan.hedberg@gmail•com>
Subject: Re: [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs
Date: Fri, 22 Feb 2019 10:05:46 -0800 [thread overview]
Message-ID: <20190222180546.GB223791@google.com> (raw)
In-Reply-To: <20190222003403.128243-2-briannorris@chromium.org>
On Thu, Feb 21, 2019 at 04:34:02PM -0800, Brian Norris wrote:
> There are two USB PID/VID variations I've seen for this chip, and I want
> to utilize the 'interrupts' property defined here already.
>
> Signed-off-by: Brian Norris <briannorris@chromium•org>
> ---
> Documentation/devicetree/bindings/net/btusb.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/btusb.txt b/Documentation/devicetree/bindings/net/btusb.txt
> index 37d67926dd6d..43c96c3380a6 100644
> --- a/Documentation/devicetree/bindings/net/btusb.txt
> +++ b/Documentation/devicetree/bindings/net/btusb.txt
> @@ -9,6 +9,9 @@ Required properties:
> (more may be added later) are:
>
> "usb1286,204e" (Marvell 8997)
> + "usb0cf3,e300" (Qualcomm QCA6174A)
> + "usb04ca,301a" (Qualcomm QCA6174A (Lite-On))
> +
>
> Also, vendors that use btusb may have device additional properties, e.g:
> Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt
Reviewed-by: Matthias Kaehlcke <mka@chromium•org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-22 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 0:34 [PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties Brian Norris
2019-02-22 0:34 ` [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs Brian Norris
2019-02-22 18:05 ` Matthias Kaehlcke [this message]
2019-02-22 21:57 ` Robin Murphy
2019-02-22 22:10 ` Brian Norris
2019-02-22 0:34 ` [PATCH 3/3] arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node Brian Norris
2019-02-22 18:27 ` Matthias Kaehlcke
2019-02-22 23:16 ` Rajat Jain
2019-02-22 18:04 ` [PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties Matthias Kaehlcke
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=20190222180546.GB223791@google.com \
--to=mka@chromium$(echo .)org \
--cc=briannorris@chromium$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dianders@chromium$(echo .)org \
--cc=enric.balletbo@collabora$(echo .)com \
--cc=heiko@sntech$(echo .)de \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=marcel@holtmann$(echo .)org \
--cc=rajatja@google$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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