From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, christoph.muellner@theobroma-systems.com,
robin.murphy@arm.com, linux-arm-kernel@lists.infradead.org,
kever.yang@rock-chips.com, linux-kernel@vger.kernel.org,
jbx6244@gmail.com
Subject: Re: [PATCH v2 3/3] arm64: dts: rockchip: add Odroid Advance Go
Date: Sun, 08 Mar 2020 23:39:35 +0100 [thread overview]
Message-ID: <2618559.AJtVb54S78@phil> (raw)
In-Reply-To: <20200308223250.353053-3-heiko@sntech.de>
Am Sonntag, 8. März 2020, 23:32:50 CET schrieb Heiko Stuebner:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> The Odroid Advance Go is a handheld based on Rockchip's rk3326 soc
> with a DSI display and some handheld controls including an analog
> joystick connected to the saradc.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> + * *** ODROIDGO2-Advance Switch layoout ***
It was pointed out to me that there is a typo here, layout instead
of layoout ;-) .
I'll hopefully just remember to remove that when applying, if I don't
need a v3 for other things.
> + * |------------------------------------------------|
> + * | sw15 sw16 |
> + * |------------------------------------------------|
> + * | sw1 |-------------------| sw8 |
> + * | sw3 sw4 | | sw7 sw5 |
> + * | sw2 | LCD Display | sw6 |
> + * | | | |
> + * | |-------------------| |
> + * | sw9 sw10 sw11 sw12 sw13 sw14 |
> + * |------------------------------------------------|
> + */
> +
prev parent reply other threads:[~2020-03-08 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 22:32 [PATCH v2 1/3] arm64: dts: rockchip: add core devicetree for rk3326 Heiko Stuebner
2020-03-08 22:32 ` [PATCH v2 2/3] dt-bindings: Add binding for Hardkernel Odroid Go Advance Heiko Stuebner
2020-03-23 19:55 ` Rob Herring
2020-03-08 22:32 ` [PATCH v2 3/3] arm64: dts: rockchip: add Odroid Advance Go Heiko Stuebner
2020-03-08 22:39 ` Heiko Stuebner [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=2618559.AJtVb54S78@phil \
--to=heiko@sntech.de \
--cc=christoph.muellner@theobroma-systems.com \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@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;
as well as URLs for NNTP newsgroup(s).