From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 0/3] arm64: dts: meson-gxl: add support for phicomm n1
Date: Fri, 9 Nov 2018 10:45:05 +0100 [thread overview]
Message-ID: <8bf8eda1-3e31-a2d8-b819-44cd2c445ae9@baylibre.com> (raw)
In-Reply-To: <20181105172825.erlq7h5ddkptthqz@raspberrypi>
Hi,
On 05/11/2018 18:28, He Yangxuan wrote:
> This patch adds support for the Phicomm N1. This device based on P230 reference design.
> The phy is RTL8211F, need to disable Energy Efficient Ethernet (EEE) to make it stable.
> And this box doesn't have cvbs, so disable related section in device tree.
Thanks for the re-spin, but :
- please fix git send-email, so the patches are linked by the Message-Id and it's simpler for us to group the patchs in our mail clients and Patchwork
- please also allways CC linux-arm-kernel at lists.infradead.org linux-kernel at vger.kernel.org
- you will need to also CC devicetree at vger.kernel.org for the bindings patches (2 & 3)
Thanks,
Neil
>
> Changes since v2:
> - remove changes section in commit message
> - add commit message for patch of vendor prefix and bindings documentation
>
> Changes since v1:
> - rewrite external phy section
> - add phicomm vendor prefix
> - add phicomm n1 in Documentation/devicetree/bindings/arm/amlogic.txt
>
> He Yangxuan (3):
> arm64: dts: meson-gxl: add support for phicomm n1
> dt-bindings: Add vendor prefix for PHICOMM Co., Ltd.
> dt-bindings: arm: amlogic: Add Phicomm N1
>
> Documentation/devicetree/bindings/arm/amlogic.txt | 1 +
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> arch/arm64/boot/dts/amlogic/Makefile | 1 +
> .../dts/amlogic/meson-gxl-s905d-phicomm-n1.dts | 26 ++++++++++++++++++++++
> 4 files changed, 29 insertions(+)
> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxl-s905d-phicomm-n1.dts
>
prev parent reply other threads:[~2018-11-09 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 17:28 He Yangxuan
2018-11-09 9:45 ` Neil Armstrong [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=8bf8eda1-3e31-a2d8-b819-44cd2c445ae9@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®