From: Alexandru M Stan <amstan@chromium.org>
To: heiko@sntech.de, roger.chen@rock-chips.com
Cc: dianders@chromium.org, peppe.cavallaro@st.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, kever.yang@rock-chips.com,
eddie.cai@rock-chips.com, Alexandru M Stan <amstan@chromium.org>,
Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] ARM: dts: rockchip: disable gmac by default in rk3288.dtsi
Date: Fri, 13 Mar 2015 17:55:31 -0700 [thread overview]
Message-ID: <1426294532-32078-1-git-send-email-amstan@chromium.org> (raw)
The way it is right now, each board using rk3288.dtsi has to disable
it or else (given CONFIG_DWMAC_RK is set) it will try loading the driver
and looking for phy's even though none are connected.
The status should be "disabled".
PS: I'm ok with "the big relicensing"
(http://www.spinics.net/lists/arm-kernel/msg403629.html) to GPLv2/X11.
Alexandru M Stan (1):
ARM: dts: rockchip: disable gmac by default in rk3288.dtsi
arch/arm/boot/dts/rk3288.dtsi | 1 +
1 file changed, 1 insertion(+)
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-03-14 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 0:55 Alexandru M Stan [this message]
[not found] ` <1426294532-32078-1-git-send-email-amstan-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2015-03-14 0:55 ` [PATCH] ARM: dts: rockchip: disable gmac by default in rk3288.dtsi Alexandru M Stan
2015-03-14 18:40 ` Heiko Stuebner
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=1426294532-32078-1-git-send-email-amstan@chromium.org \
--to=amstan@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=eddie.cai@rock-chips.com \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--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=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=roger.chen@rock-chips.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).