From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap4-droid4: add bluetooth
Date: Tue, 16 May 2017 09:34:59 -0700 [thread overview]
Message-ID: <20170516163459.GK31418@atomide.com> (raw)
In-Reply-To: <20170415221832.16175-1-sre@kernel.org>
* Sebastian Reichel <sre@kernel.org> [170415 15:21]:
> Droid 4 has wl1835 connected to the OMAP's UART4 port, which is
> used for Bluetooth and most likely can also be used for controlling
> the FM radio and GPS receivers.
...
> --- a/arch/arm/boot/dts/omap4-droid4-xt894.dts
> +++ b/arch/arm/boot/dts/omap4-droid4-xt894.dts
> @@ -395,6 +395,15 @@
> >;
> };
>
> + uart4_pins: pinmux_uart4_pins {
> + pinctrl-single,pins = <
> + OMAP4_IOPAD(0x15c, PIN_INPUT | MUX_MODE0) /* uart4_rx */
> + OMAP4_IOPAD(0x15e, PIN_OUTPUT | MUX_MODE0) /* uart4_tx */
> + OMAP4_IOPAD(0x110, PIN_INPUT_PULLUP | MUX_MODE5) /* uart4_cts */
> + OMAP4_IOPAD(0x112, PIN_OUTPUT_PULLUP | MUX_MODE5) /* uart4_rts */
> + >;
> + };
> +
> mcbsp2_pins: pinmux_mcbsp2_pins {
> pinctrl-single,pins = <
> OMAP4_IOPAD(0x0f6, PIN_INPUT | MUX_MODE0) /* abe_mcbsp2_clkx */
This needs updating against v4.12-rc1 BTW, looks like you have
some audio patches in works here that mainline does not have
for mcbsp2.
Regards,
Tony
prev parent reply other threads:[~2017-05-16 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 22:18 [PATCH] ARM: dts: omap4-droid4: add bluetooth Sebastian Reichel
2017-04-15 22:18 ` Sebastian Reichel
2017-04-16 1:56 ` Rob Herring
[not found] ` <CAEz3QY0duPa91TT3e86xA=tDGppiq0UXmDzuUm2i6cXbBi9CgQ@mail.gmail.com>
2017-04-16 15:26 ` Sebastian Reichel
2017-04-17 12:51 ` Rob Herring
2017-05-16 16:34 ` Tony Lindgren [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=20170516163459.GK31418@atomide.com \
--to=tony@atomide.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.