From: David Miller <davem@davemloft.net>
To: megous@megous.com
Cc: linux-sunxi@googlegroups.com, maxime.ripard@bootlin.com,
wens@csie.org, robh+dt@kernel.org, jernej.skrabec@gmail.com,
airlied@linux.ie, daniel@ffwll.ch, mark.rutland@arm.com,
peppe.cavallaro@st.com, alexandre.torgue@st.com,
joabreu@synopsys.com, mcoquelin.stm32@gmail.com,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v7 0/6] Add support for Orange Pi 3
Date: Mon, 24 Jun 2019 10:29:27 -0700 (PDT) [thread overview]
Message-ID: <20190624.102927.1268781741493594465.davem@davemloft.net> (raw)
In-Reply-To: <20190620134748.17866-1-megous@megous.com>
From: megous@megous.com
Date: Thu, 20 Jun 2019 15:47:42 +0200
> From: Ondrej Jirman <megous@megous.com>
>
> This series implements support for Xunlong Orange Pi 3 board.
>
> - ethernet support (patches 1-3)
> - HDMI support (patches 4-6)
>
> For some people, ethernet doesn't work after reboot (but works on cold
> boot), when the stmmac driver is built into the kernel. It works when
> the driver is built as a module. It's either some timing issue, or power
> supply issue or a combination of both. Module build induces a power
> cycling of the phy.
>
> I encourage people with this issue, to build the driver into the kernel,
> and try to alter the reset timings for the phy in DTS or
> startup-delay-us and report the findings.
This is a mixture of networking and non-networking changes so it really
can't go through my tree.
I wonder how you expect this series to be merged?
Thanks.
next prev parent reply other threads:[~2019-06-24 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 13:47 [PATCH v7 0/6] Add support for Orange Pi 3 megous
2019-06-20 13:47 ` [PATCH v7 1/6] net: stmmac: sun8i: add support for Allwinner H6 EMAC megous
2019-06-20 13:47 ` [PATCH v7 2/6] net: stmmac: sun8i: force select external PHY when no internal one megous
2019-06-20 13:47 ` [PATCH v7 3/6] arm64: dts: allwinner: orange-pi-3: Enable ethernet megous
2019-06-20 13:47 ` [PATCH v7 4/6] dt-bindings: display: hdmi-connector: Support DDC bus enable megous
2019-06-20 13:47 ` [PATCH v7 5/6] drm: sun4i: Add support for enabling DDC I2C bus to sun8i_dw_hdmi glue megous
2019-06-20 15:47 ` [linux-sunxi] " Jernej Škrabec
2019-06-20 13:47 ` [PATCH v7 6/6] arm64: dts: allwinner: orange-pi-3: Enable HDMI output megous
2019-06-20 15:53 ` [linux-sunxi] [PATCH v7 0/6] Add support for Orange Pi 3 Jernej Škrabec
2019-06-20 16:34 ` Ondřej Jirman
2019-06-21 10:44 ` Ondřej Jirman
2019-06-24 17:29 ` David Miller [this message]
2019-06-24 17:46 ` Ondřej Jirman
2019-06-24 20:24 ` David Miller
2019-06-24 20:28 ` Ondřej Jirman
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=20190624.102927.1268781741493594465.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=joabreu@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=megous@megous.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).