linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Jonas Gorski <jonas.gorski@gmail.com>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/4] MIPS: BCM63xx: remove EHCI from BCM6348 boards
Date: Tue, 11 Aug 2020 18:32:42 +0200	[thread overview]
Message-ID: <CAAdtpL5mofUYsiLecDB=yb_v6rKPuKLad5d6bM2jtoMirGLg1Q@mail.gmail.com> (raw)
In-Reply-To: <20200811150117.254620-3-noltari@gmail.com>

On Tue, Aug 11, 2020 at 5:05 PM Álvaro Fernández Rojas
<noltari@gmail.com> wrote:
>
> There's no EHCI controller on BCM6348.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>

Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

> ---
>  v3: no changes.
>  v2: no changes.
>
>  arch/mips/bcm63xx/boards/board_bcm963xx.c | 3 ---
>  1 file changed, 3 deletions(-)
>
> diff --git a/arch/mips/bcm63xx/boards/board_bcm963xx.c b/arch/mips/bcm63xx/boards/board_bcm963xx.c
> index 744aa16bab12..45f1bc437245 100644
> --- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
> +++ b/arch/mips/bcm63xx/boards/board_bcm963xx.c
> @@ -285,7 +285,6 @@ static struct board_info __initdata board_96348gw_10 = {
>
>         .has_ohci0                      = 1,
>         .has_pccard                     = 1,
> -       .has_ehci0                      = 1,
>
>         .leds = {
>                 {
> @@ -338,7 +337,6 @@ static struct board_info __initdata board_96348gw_11 = {
>
>         .has_ohci0 = 1,
>         .has_pccard = 1,
> -       .has_ehci0 = 1,
>
>         .leds = {
>                 {
> @@ -441,7 +439,6 @@ static struct board_info __initdata board_FAST2404 = {
>
>         .has_ohci0                      = 1,
>         .has_pccard                     = 1,
> -       .has_ehci0                      = 1,
>  };
>
>  static struct board_info __initdata board_rta1025w_16 = {
> --
> 2.28.0
>

  reply	other threads:[~2020-08-11 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 15:01 [PATCH v3 0/4] MIPS: BCM63xx: board improvements Álvaro Fernández Rojas
2020-08-11 15:01 ` [PATCH v3 1/4] MIPS: BCM63xx: remove duplicated new lines Álvaro Fernández Rojas
2020-08-11 15:01 ` [PATCH v3 2/4] MIPS: BCM63xx: remove EHCI from BCM6348 boards Álvaro Fernández Rojas
2020-08-11 16:32   ` Philippe Mathieu-Daudé [this message]
2020-08-11 15:01 ` [PATCH v3 3/4] MIPS: BCM63xx: enable EHCI for DWV-S0 board Álvaro Fernández Rojas
2020-08-11 16:30   ` Philippe Mathieu-Daudé
2020-08-11 15:01 ` [PATCH v3 4/4] MIPS: BCM63xx: refactor board declarations Álvaro Fernández Rojas
2020-08-11 16:48   ` Philippe Mathieu-Daudé
2020-08-11 19:25     ` Philippe Mathieu-Daudé

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='CAAdtpL5mofUYsiLecDB=yb_v6rKPuKLad5d6bM2jtoMirGLg1Q@mail.gmail.com' \
    --to=f4bug@amsat.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=noltari@gmail.com \
    --cc=tsbogend@alpha.franken.de \
    /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).