linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paul.burton@mips.com>
To: "Edward Matijević" <motolav@gmail.com>
Cc: "hauke@hauke-m.de" <hauke@hauke-m.de>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] MIPS: BCM47XX: Add support for Netgear R6200 V1
Date: Fri, 26 Jul 2019 05:15:49 +0000	[thread overview]
Message-ID: <MWHPR2201MB1277530DE66C1528B65E23B0C1C00@MWHPR2201MB1277.namprd22.prod.outlook.com> (raw)
In-Reply-To: <6e003471-e7bd-6e0a-c00c-7de5e1b01428@gmail.com>

Hello,

Edward Matijević wrote:
> The Netgear R6200 v1 uses a BCM4718A1 SOC and a BCM4352/BCM4360 for 5GHz wireless.
> This patch adds support for detecting this model board and registers the 3 buttons.
> I have tested that the device can boot kernels 4.14 and 4.19 under OpenWRT.
> 
> There is one issue that the LEDs on the device are controlled by a 74HC164 that uses bit-banging instead of SPI so it isn't accessible to the kernel without adding a workaround.
> Without any workaround the device on boot will flash all LEDs once then the power LED will remain amber as all other LEDs stay off.
> 
> I placed my change in board.c in that location because in OpenWRT it would be above the R6300 V1 in one of their patches.
> 
> Signed-off-by: Edward Matijevic <motolav@gmail.com>
> Acked-by: Hauke Mehrtens <hauke@hauke-m.de>

Applied to mips-next.

Thanks,
    Paul

[ This message was auto-generated; if you believe anything is incorrect
  then please email paul.burton@mips.com to report it. ]

      parent reply	other threads:[~2019-07-26  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  5:26 [PATCH] MIPS: BCM47XX: Add support for Netgear R6200 V1 Edward Matijević
2019-06-17 20:45 ` Hauke Mehrtens
2019-06-19 23:09 ` Paul Burton
2019-07-26  5:15 ` Paul Burton [this message]

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=MWHPR2201MB1277530DE66C1528B65E23B0C1C00@MWHPR2201MB1277.namprd22.prod.outlook.com \
    --to=paul.burton@mips.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-mips@vger.kernel.org \
    --cc=motolav@gmail.com \
    /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).