From: David Summers <beagleboard@davidjohnsummers.uk>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: mark.rutland@arm.com, linux-bluetooth@vger.kernel.org,
robh+dt@kernel.org, Johan Hedberg <johan.hedberg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] bluetooth: realtek: devicetree: Add device tree description to bluetooth rtl drivers
Date: Sat, 29 Dec 2018 16:51:29 +0000 [thread overview]
Message-ID: <40484b38-efbb-4a05-23af-c9ec6920c0df@davidjohnsummers.uk> (raw)
In-Reply-To: <20181229115513.31153-1-beagleboard@davidjohnsummers.uk>
And just looking at my patch, I remember I wrote this a month or so ago,
thought it had been checked - but a couple of changes didn't make it in:
1) "bluetoooth" is spelled "bluetooth"
2) The realtek compatible should be wrapped in a "#ifdef
CONFIG_BT_HCIUART_RTL" as hci_h5 needs that to have the realtek links in
I'll make these changes in a few days, but leave this patch here - in
case there are any other comments.
Would hope to get basic nod by next week (yes know bad time for people
over Christmas), as its free time I have to do the device tree that
needs these in ...
Regards,
David.
On 29/12/2018 11:55, David Summers wrote:
> This patch add the relevent device tree handles to the bluetooth driver
> for serial realtek devices.
>
> Specifically it takes all devices listed in btrtk.c identifes from the
> realtek web site which are serial devices (this invariably means
> devices that end with and "s" in the device name).
>
> Most of these devices are dual wifi and bluetooth, with wifi on and
> sdio connection, and bluetooth on a serial uart. As these two
> interfaces will need independent listings in the device tree, the
> nodes here have "-bluetooth" added. The only exception is the
> rtl8761atv device, which is bluetooth only - and only has a uart
> interface.
>
> Can devicetree people revive the naming scheme used here, and confirm
> it is acceptable.
>
> Marcel, if the device tree people are happy can you apply to the
> bluetooth tree.
>
> Thanks,
>
> David.
>
> Signed-off-by: David Summers <beagleboard@davidjohnsummers.uk>
> ---
> drivers/bluetooth/hci_h5.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
> index 8eede1197cd2..61c9e729efc1 100644
> --- a/drivers/bluetooth/hci_h5.c
> +++ b/drivers/bluetooth/hci_h5.c
> @@ -925,6 +925,20 @@ static struct h5_vnd rtl_vnd = {
> };
> #endif
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id h5_of_match[] = {
> + { .compatible = "realtek,rtl8723as-bluetoooth"},
> + { .compatible = "realtek,rtl8723bs-bluetoooth"},
> + { .compatible = "realtek,rtl8723ds-bluetoooth"},
> + { .compatible = "realtek,rtl8761atv"},
> + { .compatible = "realtek,rtl8821as-bluetoooth"},
> + { .compatible = "realtek,rtl8821cs-bluetoooth"},
> + { .compatible = "realtek,rtl8822bs-bluetoooth"},
> + { }
> +};
> +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
_______________________________________________
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:[~2018-12-29 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 11:55 [PATCH] bluetooth: realtek: devicetree: Add device tree description to bluetooth rtl drivers David Summers
2018-12-29 16:51 ` David Summers [this message]
2018-12-30 10:25 ` Marcel Holtmann
2019-01-03 16:35 ` [PATCHv2] Description of the realtek bluetooth device tree hooks David Summers
2019-01-03 16:35 ` [PATCHv2] Patch to add the realtek bluetooth device tree refs to the code David Summers
2019-01-18 10:57 ` Marcel Holtmann
2019-01-19 13:18 ` beagleboard
2019-01-11 16:34 ` [PATCHv2] Description of the realtek bluetooth device tree hooks Rob Herring
2019-01-12 15:00 ` David Summers
2019-01-15 19:48 ` Rob Herring
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=40484b38-efbb-4a05-23af-c9ec6920c0df@davidjohnsummers.uk \
--to=beagleboard@davidjohnsummers.uk \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).