From: Andre Przywara <andre.przywara@arm.com>
To: jagan@openedev.com, maxime.ripard@free-electrons.com,
Jagan Teki <jagannadh.teki@gmail.com>
Cc: Chen-Yu Tsai <wens@csie.org>, Sean Wang <sean.wang@mediatek.com>,
Icenowy Zheng <icenowy@aosc.io>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [linux-sunxi] Re: [PATCH v2] arm64: allwinner: a64: Add initial NanoPi A64 support
Date: Fri, 9 Jun 2017 16:36:09 +0100 [thread overview]
Message-ID: <3b4dda48-c403-88c4-5c89-63753f508d76@arm.com> (raw)
In-Reply-To: <3049841d-36f0-a761-fbed-57971462697c@openedev.com>
Hi,
On 09/06/17 16:26, Jagan Teki wrote:
> On Friday 09 June 2017 08:21 PM, Maxime Ripard wrote:
>> Hi Jagan,
>>
>> On Fri, Jun 09, 2017 at 12:40:52PM +0000, Jagan Teki wrote:
>>> +&i2c1 {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&i2c1_pins>;
>>> + status = "okay";
>>> +};
>>> +
>>> +&i2c1_pins {
>>> + bias-pull-up;
>>> +};
>>
>> What is connected on that bus?
>
> i2c1 connected with gpio/i2s
Those are the I2C pins connected to the headers. We have them in the
other A64 DTs as well (Pine64, BananaPi).
If that is not the right approach, we should discuss this and keep it
consistent at least across the A64 boards.
>>
>>> +&uart1 {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>;
>>> + status = "okay";
>>> +};
>>
>> And on that UART?
>
> uart1 for SDIO (Wifi connector, with RTS/CTS), this along with mmc1
To be precise, UART1 (with h/w handshake) is connected to the Bluetooth
part of the WiFi/BT chip, which is soldered on that board. Regardless of
the actual *WiFi* support state BT should work already - at least it did
when I tried this a few months ago on the Pine64 (although this involved
some userland heavy lifting).
Not sure what the approach here is in regard to the power supply and
wake-up GPIOs, shall they be described in this node as well or is that
up for userspace to control?
Cheers,
Andre.
next prev parent reply other threads:[~2017-06-09 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 12:40 [PATCH] arm64: allwinner: sun50i-a64: Remove duplicate ethernet@1c30000 Jagan Teki
2017-06-09 12:40 ` [PATCH v2] arm64: allwinner: a64: Add initial NanoPi A64 support Jagan Teki
2017-06-09 14:51 ` Maxime Ripard
2017-06-09 15:26 ` [linux-sunxi] " Jagan Teki
2017-06-09 15:36 ` Andre Przywara [this message]
2017-06-09 17:36 ` Andreas Färber
2017-06-10 20:28 ` Maxime Ripard
2017-06-09 13:38 ` [linux-sunxi] [PATCH] arm64: allwinner: sun50i-a64: Remove duplicate ethernet@1c30000 Andre Przywara
2017-06-09 13:58 ` Maxime Ripard
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=3b4dda48-c403-88c4-5c89-63753f508d76@arm.com \
--to=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=jagan@openedev.com \
--cc=jagannadh.teki@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=wens@csie.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®