From: Adam Ford <aford173@gmail.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Tony Lindgren <tony@atomide.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel@collabora.com,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCHv2 1/4] ARM: dts: LogicPD Torpedo: Add WiLink UART node
Date: Thu, 3 Oct 2019 16:40:26 -0500 [thread overview]
Message-ID: <CAHCN7xLtHcU6q8_dorZOySPaQATce9qbvzcK1Tn0MoEF+tURHA@mail.gmail.com> (raw)
In-Reply-To: <20191003134147.9458-2-sre@kernel.org>
On Thu, Oct 3, 2019 at 8:42 AM Sebastian Reichel <sre@kernel.org> wrote:
>
> From: Sebastian Reichel <sebastian.reichel@collabora.com>
>
> Add a node for the UART part of WiLink chip.
Thank you.
hci0: Type: Primary Bus: UART
BD Address: 00:18:30:49:7D:63 ACL MTU: 1021:4 SCO MTU: 180:4
UP RUNNING
RX bytes:6185 acl:0 sco:0 events:581 errors:0
TX bytes:91006 acl:0 sco:0 commands:578 errors:0
>
> This is compile tested only!
>
I am not sure which is more appropriate,
Acked-by: Adam Ford <aford173@gmail.com>
Tested-by: Adam Ford <aford173@gmail.com>
> Cc: Adam Ford <aford173@gmail.com>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
> arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
> index 18c27e85051f..c34ba0ef8b4d 100644
> --- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
> +++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
> @@ -50,6 +50,14 @@
> };
> };
>
> +&uart2 {
> + bluetooth {
> + compatible = "ti,wl1283-st";
> + enable-gpios = <&gpio6 2 GPIO_ACTIVE_HIGH>; /* gpio 162 */
> + max-speed = <3000000>;
> + };
> +};
> +
> &omap3_pmx_core {
> mmc3_pins: pinmux_mm3_pins {
> pinctrl-single,pins = <
> --
> 2.23.0
>
next prev parent reply other threads:[~2019-10-03 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 13:41 [PATCHv2 0/4] Convert all btwilink users to hci_ll and drop btwilink Sebastian Reichel
2019-10-03 13:41 ` [PATCHv2 1/4] ARM: dts: LogicPD Torpedo: Add WiLink UART node Sebastian Reichel
2019-10-03 21:40 ` Adam Ford [this message]
2019-10-03 13:41 ` [PATCHv2 2/4] ARM: dts: IGEP: " Sebastian Reichel
2019-10-03 13:41 ` [PATCHv2 3/4] ARM: OMAP2+: pdata-quirks: drop TI_ST/KIM support Sebastian Reichel
2019-10-03 13:41 ` [PATCHv2 4/4] Bluetooth: btwilink: drop superseded driver Sebastian Reichel
2019-10-16 19:15 ` Marcel Holtmann
2019-10-20 20:59 ` Sebastian Reichel
2019-10-21 15:14 ` Marcel Holtmann
2019-10-23 12:27 ` Sebastian Reichel
2019-10-23 12:42 ` Marcel Holtmann
2019-10-08 14:31 ` [PATCHv2 0/4] Convert all btwilink users to hci_ll and drop btwilink Tony Lindgren
2019-10-20 20:33 ` Sebastian Reichel
2019-10-22 16:01 ` Tony Lindgren
2019-10-23 12:06 ` Sebastian Reichel
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=CAHCN7xLtHcU6q8_dorZOySPaQATce9qbvzcK1Tn0MoEF+tURHA@mail.gmail.com \
--to=aford173@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sebastian.reichel@collabora.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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).