From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 2/3] ARM64: dts: meson-gxbb: Add support for WeTek Hub and Play
Date: Thu, 19 Jan 2017 09:12:20 +0100 [thread overview]
Message-ID: <61c3c24d-57cd-b81d-0225-5aae14352397@baylibre.com> (raw)
In-Reply-To: <m2mveox9mm.fsf@baylibre.com>
On 01/18/2017 11:53 PM, Kevin Hilman wrote:
> Neil Armstrong <narmstrong@baylibre.com> writes:
>
>> Adds support for the WeTek Hub and Play2 boards.
>> The Hub is an extremely small IPTv Set-Top-Box and the Play2 is a more
>> traditionnal Satellite or Terrestrial and IPTv Set-Top-Box.
>>
>> Both are based on the p200 Reference Design and out-of-tree support is
>> based on OpenELEC kernel at [1].
>>
>> [1] https://github.com/wetek-enigma/linux-amlogic
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>
> Did you get the GPIO/button info from the LibreELEC tree or did you find
> some schematics someplace? If you found any schematics, it would be
> nice to have links in the DTS files.
>
> Kevin
>
It was in the dts of the LibreELEC tree, I found no schematics so far.
I can respin a v2 with a link to the LibreELEC dts files.
Neil
next prev parent reply other threads:[~2017-01-19 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:50 [PATCH 0/3] ARM64: meson-gxbb: Add WeTek Boards Neil Armstrong
2017-01-18 10:50 ` [PATCH 1/3] dt-bindings: vendor-prefix: Add wetek vendor prefix Neil Armstrong
2017-01-21 20:29 ` Rob Herring
2017-01-18 10:50 ` [PATCH 2/3] ARM64: dts: meson-gxbb: Add support for WeTek Hub and Play Neil Armstrong
2017-01-18 22:53 ` Kevin Hilman
2017-01-19 8:12 ` Neil Armstrong [this message]
2017-01-19 18:02 ` Kevin Hilman
2017-01-18 10:50 ` [PATCH 3/3] dt-bindings: amlogic: Add WeTek boards Neil Armstrong
2017-01-21 20:30 ` Rob Herring
2017-01-20 15:50 ` [PATCH 0/3] ARM64: meson-gxbb: Add WeTek Boards Kevin Hilman
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=61c3c24d-57cd-b81d-0225-5aae14352397@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®