linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Ondřej Jirman" <megous@megous.com>
To: David Miller <davem@davemloft.net>
Cc: mark.rutland@arm.com, joabreu@synopsys.com,
	alexandre.torgue@st.com, devicetree@vger.kernel.org,
	maxime.ripard@bootlin.com, netdev@vger.kernel.org, wens@csie.org,
	jernej.skrabec@gmail.com, linux-kernel@vger.kernel.org,
	airlied@linux.ie, linux-sunxi@googlegroups.com,
	robh+dt@kernel.org, dri-devel@lists.freedesktop.org,
	daniel@ffwll.ch, peppe.cavallaro@st.com,
	linux-stm32@st-md-mailman.stormreply.com,
	mcoquelin.stm32@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 0/6] Add support for Orange Pi 3
Date: Mon, 24 Jun 2019 19:46:37 +0200	[thread overview]
Message-ID: <20190624174637.6sznc5ifiuh4c3sm@core.my.home> (raw)
In-Reply-To: <20190624.102927.1268781741493594465.davem@davemloft.net>

On Mon, Jun 24, 2019 at 10:29:27AM -0700, David Miller wrote:
> 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.

This series was even longer before, with patches all around for various
maintainers. I'd expect that relevant maintainers pick the range of patches
meant for them. I don't know who's exactly responsible for what, but I think,
this should work:

- 2 stmmac patches should go together via some networking tree (is there
  something specific for stmmac?)
- all DTS patches should go via sunxi
- hdmi patches via some drm tree

thank you and regards,
	o.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-06-24 17:46 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
2019-06-24 17:46   ` Ondřej Jirman [this message]
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=20190624174637.6sznc5ifiuh4c3sm@core.my.home \
    --to=megous@megous.com \
    --cc=airlied@linux.ie \
    --cc=alexandre.torgue@st.com \
    --cc=daniel@ffwll.ch \
    --cc=davem@davemloft.net \
    --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=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).