From: john@phrozen.org (John Crispin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: dts: mt7623: Add initial Geek Force support
Date: Thu, 12 Jan 2017 09:23:14 +0100 [thread overview]
Message-ID: <0bd6567e-1c5b-0ff6-d044-57d25e1a40d2@phrozen.org> (raw)
In-Reply-To: <3fecb422-8185-7ee0-c203-2bfdc4fd1393@phrozen.org>
Hi Andreas,
had a look last night why the ethernet dtsi was not added and it
obviously was not added as we were waiting for the clk-mt2701 to be
merged. the ethernet dtsi will have phandles pointing at the clk nodes
which did not exist at the time. same is true for the PWM code.
i sat down last night and worked out what pending patches i still have
for mt7623 and out of the ~80 required to get v4.4 working i only need
around 10 for v4.10-rc1.
i started to rebase these patches last night and will have time to test
them tomorrow or early next week. as the pwrap node alone is around 200
lines of devicetree we need to figure out a way to add this to the dts
files without duplicating it. i'll try to post a series early next week
that we can then discuss and rebase your geekboard patches on.
John
next prev parent reply other threads:[~2017-01-12 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 13:30 [PATCH 0/4] ARM: dts: mt7623: Add initial Geek Force support Andreas Färber
2017-01-08 13:30 ` [PATCH 1/4] Documentation: devicetree: Add vendor prefix for AsiaRF Andreas Färber
2017-01-10 5:35 ` Rob Herring
2017-01-08 13:30 ` [PATCH 2/4] Documentation: devicetree: arm: mediatek: Add Geek Force board Andreas Färber
2017-01-10 5:36 ` Rob Herring
2017-01-08 13:30 ` [PATCH 3/4] ARM: dts: mt7623: Add Geek Force config Andreas Färber
2017-01-08 13:31 ` [PATCH 4/4] MAINTAINERS: Extend ARM/Mediatek SoC support section Andreas Färber
2017-01-10 7:00 ` [PATCH 0/4] ARM: dts: mt7623: Add initial Geek Force support John Crispin
2017-01-10 9:48 ` Andreas Färber
2017-01-10 10:18 ` John Crispin
2017-01-12 8:23 ` John Crispin [this message]
2017-01-16 19:34 ` Andreas Färber
2017-01-16 19:31 ` Andreas Färber
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=0bd6567e-1c5b-0ff6-d044-57d25e1a40d2@phrozen.org \
--to=john@phrozen.org \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).