From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: kirkwood: Fix SATA pinmux-ing for TS419
Date: Mon, 20 Feb 2017 17:50:49 +0100 [thread overview]
Message-ID: <20170220175049.45f319bb@free-electrons.com> (raw)
In-Reply-To: <1487608825.2885.1.camel@decadent.org.uk>
Hello,
On Mon, 20 Feb 2017 16:40:25 +0000, Ben Hutchings wrote:
> That is precisely what I intended. 20-23 are used by the second
> Ethernet port. The old board code doesn't assign 4 or 5 at all.
Then I believe it would be more explicit to have separate pin muxing
configurations for SATA on this board.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 0:32 [PATCH] ARM: dts: kirkwood: Fix SATA pinmux-ing for TS419 Ben Hutchings
2017-02-20 12:59 ` Thomas Petazzoni
2017-02-20 16:40 ` Ben Hutchings
2017-02-20 16:50 ` Thomas Petazzoni [this message]
2017-02-20 17:22 ` Ben Hutchings
2017-02-20 20:31 ` Thomas Petazzoni
2017-03-07 17:16 ` Gregory CLEMENT
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=20170220175049.45f319bb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@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