[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190222180406.GA223791@google.com>
Date: Fri, 22 Feb 2019 10:04:06 -0800
From: Matthias Kaehlcke <mka@...omium.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Heiko Stuebner <heiko@...ech.de>,
Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Douglas Anderson <dianders@...omium.org>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
Rajat Jain <rajatja@...gle.com>
Subject: Re: [PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties
On Thu, Feb 21, 2019 at 04:34:01PM -0800, Brian Norris wrote:
> We may need to specify a GPIO wake pin for this device, so add a
> compatible property for it.
>
> There are at least to USB PID/VID variations of this chip: one with a
> Lite-On ID and one with an Atheros ID.
>
> Signed-off-by: Brian Norris <briannorris@...omium.org>
> ---
> drivers/bluetooth/btusb.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 470ee68555d9..380e6f38c607 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -2862,6 +2862,8 @@ static irqreturn_t btusb_oob_wake_handler(int irq, void *priv)
>
> static const struct of_device_id btusb_match_table[] = {
> { .compatible = "usb1286,204e" },
> + { .compatible = "usb0cf3,e300" }, /* QCA6174A */
> + { .compatible = "usb04ca,301a" }, /* QCA6174A (Lite-On) */
> { }
> };
> MODULE_DEVICE_TABLE(of, btusb_match_table);
Reviewed-by: Matthias Kaehlcke <mka@...omium.org>
Powered by blists - more mailing lists