public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Philip Balister <philip@opensdr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: Overo: Update GPMC timing for ethernet chip.
Date: Thu, 08 Sep 2011 14:50:19 -0400	[thread overview]
Message-ID: <4E690E6B.1040106@opensdr.com> (raw)
In-Reply-To: <CAFqH_51K6hrixxKPh8ZWK+KC0FyDk=eQF5w6rA2EZGnvKTO8xA@mail.gmail.com>

On 09/08/2011 10:45 AM, Enric Balletb? i Serra wrote:
> 2011/9/8 Steve Sakoman<sakoman@gmail.com>:
>> On Wed, Sep 7, 2011 at 4:57 AM, Philip Balister<philip@balister.org>  wrote:
>>> The existing timing does not quite meet the minimum requirements
>>> in the LAN9221 datasheet. The timing in this patch solves problems
>>> noticed on some parts.
>>>
>>> Signed-off-by: Philip Balister<philip@opensdr.com>
>>
>> Acked-by: Steve Sakoman<steve@sakoman.com>
>> Tested-by: Steve Sakoman<steve@sakoman.com>
>>
>>> ---
>>>   board/overo/overo.h |    6 +++---
>>>   1 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/board/overo/overo.h b/board/overo/overo.h
>>> index 68e1243..617c0c3 100644
>>> --- a/board/overo/overo.h
>>> +++ b/board/overo/overo.h
>>> @@ -35,10 +35,10 @@ const omap3_sysinfo sysinfo = {
>>>
>>>   /* GPMC CS 5 connected to an SMSC LAN9221 ethernet controller */
>>>   #define NET_LAN9221_GPMC_CONFIG1    0x00001000
>>> -#define NET_LAN9221_GPMC_CONFIG2    0x00080701
>>> +#define NET_LAN9221_GPMC_CONFIG2    0x00060700
>>>   #define NET_LAN9221_GPMC_CONFIG3    0x00020201
>>> -#define NET_LAN9221_GPMC_CONFIG4    0x08030703
>>> -#define NET_LAN9221_GPMC_CONFIG5    0x00060908
>>> +#define NET_LAN9221_GPMC_CONFIG4    0x06000700
>>> +#define NET_LAN9221_GPMC_CONFIG5    0x0006090A
>>>   #define NET_LAN9221_GPMC_CONFIG6    0x87030000
>>>   #define NET_LAN9221_GPMC_CONFIG7    0x00000f6c
>>>
>>> --
>>> 1.7.4.4
>>>
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot
>>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>
> Other boards like IGEP v2 board uses the same LAN9221 ethernet
> controller, so this code is duplicated on overo.h and igep0020.h
> files. Maybe could be a good idea move this part to
> arch/arm/include/asm/arch-omap3/omap_gpmc.h or another file to not
> duplicate the code.

Is there anyone around with an igep v2 board who could test/ack such a 
patch?

Philip

  reply	other threads:[~2011-09-08 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 11:57 [U-Boot] [PATCH] net: Add \n before warning message so it prints on a new line Philip Balister
2011-09-07 11:57 ` [U-Boot] [PATCH] OMAP3: Overo: Update GPMC timing for ethernet chip Philip Balister
2011-09-08 14:21   ` Steve Sakoman
2011-09-08 14:45     ` Enric Balletbò i Serra
2011-09-08 18:50       ` Philip Balister [this message]
2011-09-08 19:48         ` Enric Balletbò i Serra
2011-09-07 11:57 ` [U-Boot] [PATCH] overo: Set IEN on GPMC_CLK to support CS's that use synchronous clocking Philip Balister
2011-09-08 15:01 ` [U-Boot] [PATCH] net: Add \n before warning message so it prints on a new line Albert ARIBAUD
2011-09-08 15:04   ` Philip Balister
2011-09-08 16:08     ` Albert ARIBAUD

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=4E690E6B.1040106@opensdr.com \
    --to=philip@opensdr.com \
    --cc=u-boot@lists.denx.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