public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Bernhard Walle <walle@corscience.de>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: Add Lanai board USB clock type
Date: Mon, 11 Oct 2010 09:53:05 -0700	[thread overview]
Message-ID: <4CB340F1.8020000@caviumnetworks.com> (raw)
In-Reply-To: <1286791747-3151-1-git-send-email-walle@corscience.de>

On 10/11/2010 03:09 AM, Bernhard Walle wrote:
> Add the LANAI2 board to __cvmx_helper_board_usb_get_clock_type(). It
> also uses the USB_CLOCK_TYPE_CRYSTAL_12 clock.
>
> Signed-off-by: Bernhard Walle<walle@corscience.de>
> ---
>   drivers/staging/octeon/cvmx-helper-board.c |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)

NAK.

We don't currently support USB, so churning up this file doesn't help 
anything.

If you are using an out-of-tree driver, you can keep this kind of tweak 
out-of-tree as well.

David Daney

>
> diff --git a/drivers/staging/octeon/cvmx-helper-board.c b/drivers/staging/octeon/cvmx-helper-board.c
> index 5793318..f8ae6b4 100644
> --- a/drivers/staging/octeon/cvmx-helper-board.c
> +++ b/drivers/staging/octeon/cvmx-helper-board.c
> @@ -752,6 +752,7 @@ cvmx_helper_board_usb_clock_types_t __cvmx_helper_board_usb_get_clock_type(void)
>   {
>   	switch (cvmx_sysinfo_get()->board_type) {
>   	case CVMX_BOARD_TYPE_BBGW_REF:
> +	case CVMX_BOARD_TYPE_LANAI2_G:
>   		return USB_CLOCK_TYPE_CRYSTAL_12;
>   	}
>   	return USB_CLOCK_TYPE_REF_48;


  reply	other threads:[~2010-10-11 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 10:09 [PATCH] staging: octeon: Add Lanai board USB clock type Bernhard Walle
2010-10-11 16:53 ` David Daney [this message]
2010-10-11 17:05   ` Bernhard Walle
2010-10-11 17:13     ` David Daney
2010-10-12 15:54       ` Greg KH
2010-10-12 16:56         ` David Daney
2010-10-13 16:39           ` Bernhard Walle
2010-10-13 21:02             ` Greg KH

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=4CB340F1.8020000@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walle@corscience.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