From: David Summers <beagleboard@davidjohnsummers.uk>
To: David Summers <beagleboard@davidjohnsummers.uk>,
robh+dt@kernel.org, mark.rutland@arm.com, marcel@holtmann.org,
johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] Bluetooth: hci_h5: Add the Realtek compatible flags for the device tree
Date: Sat, 26 Jan 2019 14:28:58 +0000 [thread overview]
Message-ID: <5a99337a-c33b-7dd6-dbdb-6945ec976ea4@davidjohnsummers.uk> (raw)
In-Reply-To: <20190121203928.32723-1-beagleboard@davidjohnsummers.uk>
This patch has been withdrawn.
On 21/01/2019 20:39, David Summers wrote:
> With the changes requested by Marcel Holtmann and Rob Herring.
>
> The patch is unchanged, but subject changed to the norm.
>
> Signed-off-by: David Summers <beagleboard@davidjohnsummers.uk>
> ---
> drivers/bluetooth/hci_h5.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
> index 8eede1197cd2..056ab2decccc 100644
> --- a/drivers/bluetooth/hci_h5.c
> +++ b/drivers/bluetooth/hci_h5.c
> @@ -925,6 +925,22 @@ static struct h5_vnd rtl_vnd = {
> };
> #endif
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id h5_of_match[] = {
> +#ifdef CONFIG_BT_HCIUART_RTL
> + { .compatible = "realtek,rtl8723as-bt"},
> + { .compatible = "realtek,rtl8723bs-bt"},
> + { .compatible = "realtek,rtl8723ds-bt"},
> + { .compatible = "realtek,rtl8761atv"},
> + { .compatible = "realtek,rtl8821as-bt"},
> + { .compatible = "realtek,rtl8821cs-bt"},
> + { .compatible = "realtek,rtl8822bs-bt"},
> +#endif
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, h5_of_match);
> +#endif
> +
> #ifdef CONFIG_ACPI
> static const struct acpi_device_id h5_acpi_match[] = {
> #ifdef CONFIG_BT_HCIUART_RTL
prev parent reply other threads:[~2019-01-26 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 20:39 [PATCH v4 1/2] Bluetooth: hci_h5: Add the Realtek compatible flags for the device tree David Summers
2019-01-21 20:39 ` [PATCH v4 2/2] dt-bindings: Create the file for Realtek Bluetooth serial devices David Summers
2019-01-22 2:40 ` Chen-Yu Tsai
2019-01-25 18:55 ` David Summers
2019-01-25 19:03 ` David Summers
2019-01-25 19:46 ` Rob Herring
2019-01-26 14:26 ` David Summers
2019-01-22 2:42 ` [PATCH v4 1/2] Bluetooth: hci_h5: Add the Realtek compatible flags for the device tree Chen-Yu Tsai
2019-01-26 14:28 ` David Summers [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=5a99337a-c33b-7dd6-dbdb-6945ec976ea4@davidjohnsummers.uk \
--to=beagleboard@davidjohnsummers.uk \
--cc=devicetree@vger.kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).