Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [RFC V2][PATCH] MIPS: BCM47XX: Add new file for device specific workarounds
Date: Sun, 02 Mar 2014 17:34:15 +0100	[thread overview]
Message-ID: <53135D87.6080306@hauke-m.de> (raw)
In-Reply-To: <1391286733-14333-1-git-send-email-zajec5@gmail.com>

On 02/01/2014 09:32 PM, Rafał Miłecki wrote:
> ---
> V2: Drop pr_debug for devices we don't need workarounds for. It was too
>     load and not useful at all.
> ---

This looks good to me, feel free to add my Acked-By. You have to send it
with a Signed-off-by line.

Hauke


>  arch/mips/bcm47xx/Makefile          |  2 +-
>  arch/mips/bcm47xx/bcm47xx_private.h |  3 +++
>  arch/mips/bcm47xx/setup.c           |  1 +
>  arch/mips/bcm47xx/workarounds.c     | 25 +++++++++++++++++++++++++
>  4 files changed, 30 insertions(+), 1 deletion(-)
>  create mode 100644 arch/mips/bcm47xx/workarounds.c
> 
> diff --git a/arch/mips/bcm47xx/Makefile b/arch/mips/bcm47xx/Makefile
> index 4688b6a..d58c51b 100644
> --- a/arch/mips/bcm47xx/Makefile
> +++ b/arch/mips/bcm47xx/Makefile
> @@ -4,4 +4,4 @@
>  #
>  
>  obj-y				+= irq.o nvram.o prom.o serial.o setup.o time.o sprom.o
> -obj-y				+= board.o buttons.o leds.o
> +obj-y				+= board.o buttons.o leds.o workarounds.o
> diff --git a/arch/mips/bcm47xx/bcm47xx_private.h b/arch/mips/bcm47xx/bcm47xx_private.h
> index 5c94ace..0194c3b 100644
> --- a/arch/mips/bcm47xx/bcm47xx_private.h
> +++ b/arch/mips/bcm47xx/bcm47xx_private.h
> @@ -9,4 +9,7 @@ int __init bcm47xx_buttons_register(void);
>  /* leds.c */
>  void __init bcm47xx_leds_register(void);
>  
> +/* workarounds.c */
> +void __init bcm47xx_workarounds(void);
> +
>  #endif
> diff --git a/arch/mips/bcm47xx/setup.c b/arch/mips/bcm47xx/setup.c
> index 12d77e9..fdd9692 100644
> --- a/arch/mips/bcm47xx/setup.c
> +++ b/arch/mips/bcm47xx/setup.c
> @@ -273,6 +273,7 @@ static int __init bcm47xx_register_bus_complete(void)
>  	}
>  	bcm47xx_buttons_register();
>  	bcm47xx_leds_register();
> +	bcm47xx_workarounds();
>  
>  	return 0;
>  }
> diff --git a/arch/mips/bcm47xx/workarounds.c b/arch/mips/bcm47xx/workarounds.c
> new file mode 100644
> index 0000000..24b850c
> --- /dev/null
> +++ b/arch/mips/bcm47xx/workarounds.c
> @@ -0,0 +1,25 @@
> +#include "bcm47xx_private.h"
> +
> +#include <linux/gpio.h>
> +#include <bcm47xx_board.h>
> +#include <bcm47xx.h>
> +
> +static void __init bcm47xx_workarounds_netgear_wnr3500l(void)
> +{
> +	/* Set GPIO 12 to 1 to pass power to the USB port */
> +	gpio_set_value(12, 1);
> +}
> +
> +void __init bcm47xx_workarounds(void)
> +{
> +	enum bcm47xx_board board = bcm47xx_board_get();
> +
> +	switch (board) {
> +	case BCM47XX_BOARD_NETGEAR_WNR3500L:
> +		bcm47xx_workarounds_netgear_wnr3500l();
> +		break;
> +	default:
> +		/* No workaround(s) needed */
> +		break;
> +	}
> +}
> 

  reply	other threads:[~2014-03-02 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 20:32 [RFC V2][PATCH] MIPS: BCM47XX: Add new file for device specific workarounds Rafał Miłecki
2014-03-02 16:34 ` Hauke Mehrtens [this message]
2014-03-21  9:08 ` [PATCH V3] " Rafał Miłecki

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=53135D87.6080306@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=zajec5@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