From: Simon Horman <horms@verge.net.au>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCHv2] arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins
Date: Mon, 6 Mar 2017 09:58:01 +0100 [thread overview]
Message-ID: <20170306085801.GF11468@verge.net.au> (raw)
In-Reply-To: <20170305232818.GA20587@bigcity.dyn.berto.se>
On Mon, Mar 06, 2017 at 12:28:18AM +0100, Niklas Söderlund wrote:
> Hi Simon,
>
> On 2016-12-08 14:31:38 +0100, Simon Horman wrote:
> > On Mon, Dec 05, 2016 at 06:43:10PM +0100, Niklas Söderlund wrote:
> > > The EthernetAVB should not depend on the bootloader to setup correct
> > > drive-strength values. Values for drive-strength where found by
> > > examining the registers after the bootloader has configured the
> > > registers and successfully used the EthernetAVB.
> > >
> > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> >
> > I believe this patch has run-time dependencies on PFC patches and will
> > result in a regression without them. Please resubmit or otherwise ping me
> > once chose changes are present in an (rc) release or immutable branch.
>
> The dependency for this DT change is now present in v4.11-rc1, see 1. If
> it's convenient for you feel free to pick up this patch.
>
> 1. b25719eb938eb39a ("pinctrl: sh-pfc: r8a7795: Add group for AVB MDIO
> and MII pins")
Thanks Niklas,
I am in the process of rebasing my branches on top of v4.11-rc1
and I have queued up this patch. It should appear in the next push
of renesas-next and renesas-revel.
next prev parent reply other threads:[~2017-03-06 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 17:43 [PATCHv2] arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins Niklas Söderlund
2016-12-08 13:31 ` Simon Horman
2017-03-05 23:28 ` Niklas Söderlund
2017-03-06 8:58 ` Simon Horman [this message]
2016-12-09 10:05 ` Geert Uytterhoeven
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=20170306085801.GF11468@verge.net.au \
--to=horms@verge.net.au \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
/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