All of lore.kernel.org
 help / color / mirror / Atom feed
From: henry.nestler@gmail.com (Henry Nestler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] DM9000B: Fix PHY power for network down/up
Date: Mon, 21 Feb 2011 22:03:31 +0100	[thread overview]
Message-ID: <4D62D323.7010403@henry.nestler.mail.gmail.com> (raw)
In-Reply-To: <4D62491F.4050602@ru.mvista.com>

On 21.02.2011 12:14, Sergei Shtylyov wrote:
> On 21-02-2011 0:45, Henry Nestler wrote:
> 
>> DM9000 revision B needs 1 ms delay after PHY power on (see spec), and PHY
>> power must on in register
> 
>     Couldn't parse that.

This can read in manual DM900B-12-DS-F02 from September 2 2010, Page 14:
"If this Register 1FH bit 0 is updated from '1' to '0', the all
Registers can not be accessed within 1ms."

The example driver code waits 2 ms.

>> diff --git a/drivers/net/dm9000.c b/drivers/net/dm9000.c
>> index 2d4c4fc..5925569 100644
>> --- a/drivers/net/dm9000.c
>> +++ b/drivers/net/dm9000.c
> [...]
>> @@ -1194,6 +1191,10 @@ dm9000_open(struct net_device *dev)
>>   	if (request_irq(dev->irq, dm9000_interrupt, irqflags, dev->name, dev))
>>   		return -EAGAIN;
>>
>> +	/* GPIO0 on pre-activate PHY, Reg 1F is not set by reset */
>> +	iow(db, DM9000_GPR, 0);	/* REG_1F bit0 activate phyxcer */
>> +	udelay(1000); /* delay needs by DM9000B */
> 
>     Why not mdelay(1)?

Because udelay is the base of mdelay.
See include/linux/delay.h:31

#define mdelay(n) ... udelay((n)*1000)

-- 
Henry N.

WARNING: multiple messages have this Message-ID (diff)
From: Henry Nestler <henry.nestler@gmail.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: netdev@vger.kernel.org, tori@unhappy.mine.nu,
	akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] DM9000B: Fix PHY power for network down/up
Date: Mon, 21 Feb 2011 22:03:31 +0100	[thread overview]
Message-ID: <4D62D323.7010403@henry.nestler.mail.gmail.com> (raw)
In-Reply-To: <4D62491F.4050602@ru.mvista.com>

On 21.02.2011 12:14, Sergei Shtylyov wrote:
> On 21-02-2011 0:45, Henry Nestler wrote:
> 
>> DM9000 revision B needs 1 ms delay after PHY power on (see spec), and PHY
>> power must on in register
> 
>     Couldn't parse that.

This can read in manual DM900B-12-DS-F02 from September 2 2010, Page 14:
"If this Register 1FH bit 0 is updated from '1' to '0', the all
Registers can not be accessed within 1ms."

The example driver code waits 2 ms.

>> diff --git a/drivers/net/dm9000.c b/drivers/net/dm9000.c
>> index 2d4c4fc..5925569 100644
>> --- a/drivers/net/dm9000.c
>> +++ b/drivers/net/dm9000.c
> [...]
>> @@ -1194,6 +1191,10 @@ dm9000_open(struct net_device *dev)
>>   	if (request_irq(dev->irq, dm9000_interrupt, irqflags, dev->name, dev))
>>   		return -EAGAIN;
>>
>> +	/* GPIO0 on pre-activate PHY, Reg 1F is not set by reset */
>> +	iow(db, DM9000_GPR, 0);	/* REG_1F bit0 activate phyxcer */
>> +	udelay(1000); /* delay needs by DM9000B */
> 
>     Why not mdelay(1)?

Because udelay is the base of mdelay.
See include/linux/delay.h:31

#define mdelay(n) ... udelay((n)*1000)

-- 
Henry N.

  reply	other threads:[~2011-02-21 21:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 21:45 [PATCH 2/2] DM9000B: Fix PHY power for network down/up Henry Nestler
2011-02-20 21:45 ` Henry Nestler
2011-02-21 11:14 ` Sergei Shtylyov
2011-02-21 11:14   ` Sergei Shtylyov
2011-02-21 21:03   ` Henry Nestler [this message]
2011-02-21 21:03     ` Henry Nestler
2011-02-22 12:36     ` Sergei Shtylyov
2011-02-22 12:36       ` Sergei Shtylyov
2011-02-22 18:24     ` David Miller
2011-02-22 18:24       ` David Miller
2011-02-22 19:58       ` Henry Nestler
2011-02-22 19:58         ` Henry Nestler
2011-02-22 21:29       ` [PATCHv2 " Henry Nestler
2011-02-22 21:29         ` Henry Nestler
2011-02-23 22:30         ` David Miller
2011-02-23 22:30           ` David Miller

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=4D62D323.7010403@henry.nestler.mail.gmail.com \
    --to=henry.nestler@gmail.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.