Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mathias Kresin <dev@kresin.me>
To: ralf@linux-mips.org
Cc: john@phrozen.org, linux-mips@linux-mips.org
Subject: [PATCH 1/2] MIPS: ralink: fix MT7628 pinmux
Date: Thu, 11 May 2017 08:11:14 +0200	[thread overview]
Message-ID: <1494483075-17816-1-git-send-email-dev@kresin.me> (raw)

According to the datasheet the REFCLK pin is shared with GPIO#37 and
the PERST pin is shared with GPIO#36.

Signed-off-by: Mathias Kresin <dev@kresin.me>
---
 arch/mips/ralink/mt7620.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/mips/ralink/mt7620.c b/arch/mips/ralink/mt7620.c
index 094a0ee..528a6ac 100644
--- a/arch/mips/ralink/mt7620.c
+++ b/arch/mips/ralink/mt7620.c
@@ -144,8 +144,8 @@ static struct rt2880_pmx_func i2c_grp_mt7628[] = {
 	FUNC("i2c", 0, 4, 2),
 };
 
-static struct rt2880_pmx_func refclk_grp_mt7628[] = { FUNC("reclk", 0, 36, 1) };
-static struct rt2880_pmx_func perst_grp_mt7628[] = { FUNC("perst", 0, 37, 1) };
+static struct rt2880_pmx_func refclk_grp_mt7628[] = { FUNC("reclk", 0, 37, 1) };
+static struct rt2880_pmx_func perst_grp_mt7628[] = { FUNC("perst", 0, 36, 1) };
 static struct rt2880_pmx_func wdt_grp_mt7628[] = { FUNC("wdt", 0, 38, 1) };
 static struct rt2880_pmx_func spi_grp_mt7628[] = { FUNC("spi", 0, 7, 4) };
 
-- 
2.7.4

             reply	other threads:[~2017-05-11  6:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  6:11 Mathias Kresin [this message]
2017-05-11  6:11 ` [PATCH 2/2] MIPS: ralink: fix typo in mt7628 pinmux function Mathias Kresin
2017-11-12  9:56   ` John Crispin
2017-11-12  9:55 ` [PATCH 1/2] MIPS: ralink: fix MT7628 pinmux John Crispin
2017-11-13 12:25   ` James Hogan
2017-11-13 12:25     ` James Hogan

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=1494483075-17816-1-git-send-email-dev@kresin.me \
    --to=dev@kresin.me \
    --cc=john@phrozen.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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