All of lore.kernel.org
 help / color / mirror / Atom feed
From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] net/fec: iMX53 needs gasket for both MII and RMII
Date: Wed, 29 Jun 2011 15:50:56 -0700	[thread overview]
Message-ID: <4E0BAC50.3030007@boundarydevices.com> (raw)
In-Reply-To: <1309387098-30680-1-git-send-email-troy.kisky@boundarydevices.com>

On 6/29/2011 3:38 PM, Troy Kisky wrote:
> Currently, only RMII interfaces are using the gasket.
> But, the iMX53 needs to enable the gasket for MII
> mode as well. The iMX51 has no gasket registers. So,
> add a use_gasket field to fec_platform_data to not restrict
> same kernel for both iMX51/53 boards.
> 
> iMX28 boards don't need use_gasket, as they have
> FEC_QUIRK_ENET_MAC.
> ---
>  arch/arm/mach-mx5/board-mx50_rdp.c  |    1 +
>  arch/arm/mach-mx5/board-mx53_evk.c  |    1 +
>  arch/arm/mach-mx5/board-mx53_loco.c |    1 +
>  arch/arm/mach-mx5/board-mx53_smd.c  |    1 +
>  drivers/net/fec.c                   |   11 ++++++++---
>  include/linux/fec.h                 |    1 +
>  6 files changed, 13 insertions(+), 3 deletions(-)
...
> diff --git a/include/linux/fec.h b/include/linux/fec.h
> index bcff455..c0a7ad8 100644
> --- a/include/linux/fec.h
> +++ b/include/linux/fec.h
> @@ -19,6 +19,7 @@
>  struct fec_platform_data {
>  	phy_interface_t phy;
>  	unsigned char mac[ETH_ALEN];
> +	unsigned use_gasket : 1;
>  };
>  
>  #endif

I'll repost with checkpatch.pl fixes if approved.

Thanks
Troy

       reply	other threads:[~2011-06-29 22:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1309387098-30680-1-git-send-email-troy.kisky@boundarydevices.com>
2011-06-29 22:50 ` Troy Kisky [this message]
2011-06-30 19:04   ` [PATCH 1/1] net/fec: iMX53 needs gasket for both MII and RMII Fabio Estevam
2011-06-30 16:19 ` Shawn Guo
2011-06-30 18:49   ` Troy Kisky
2011-07-01 10:12     ` Shawn Guo
2011-07-01 10:11   ` [PATCH] net/fec: gasket needs to be enabled for some i.mx Shawn Guo
2011-07-01 10:11     ` Shawn Guo
2011-07-04  6:55     ` Sascha Hauer
2011-07-04  6:55       ` Sascha Hauer
2011-07-06  5:14       ` Shawn Guo
2011-07-06  5:14         ` Shawn Guo
2011-07-07 11:12     ` David Miller
2011-07-07 11:12       ` David Miller
2011-07-07 13:41       ` Shawn Guo
2011-07-07 13:41         ` Shawn Guo
2011-07-07 18:44         ` Grant Likely
2011-07-07 18:44           ` Grant Likely
2011-07-08  0:06           ` Shawn Guo
2011-07-08  0:06             ` Shawn Guo
2011-07-22  2:00             ` Shawn Guo
2011-07-22  2:00               ` Shawn Guo
2011-07-08 10:18     ` Sascha Hauer
2011-07-08 10:18       ` Sascha Hauer
2011-07-08 18:38       ` Troy Kisky
2011-07-08 18:38         ` Troy Kisky
2011-07-09  5:45         ` Shawn Guo
2011-07-09  5:45           ` Shawn Guo
2011-07-09  5:44       ` Shawn Guo
2011-07-09  5:44         ` Shawn Guo

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=4E0BAC50.3030007@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.