From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for ASIX's AX88783 ethernet chip
Date: Wed, 02 Feb 2011 19:02:11 +0100 [thread overview]
Message-ID: <4D499C23.40500@denx.de> (raw)
In-Reply-To: <1296495758-17784-1-git-send-email-lgxue@hotmail.com>
On 01/31/2011 06:42 PM, Joe Xue wrote:
> for more information about this chip, please check:
> http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=98;65;86&PLine=65
>
> Signed-off-by: Joe Xue <lgxue@hotmail.com>
>
Please add a version number to your patch to make easier tracking which
is your last version.
Do not forget to add always the net Maintainer to CC (Wolfgang Denk), I
added him now.
> --- /dev/null
> +++ b/drivers/net/ax88783.c
> @@ -0,0 +1,297 @@
> +/*
> + *
You should drop this line
> +
> +static int ax88183_phy_initial(struct eth_device *dev)
You forget to replace the name of the function. It has still ax88183_
> + /* phy init */
> + tmp = readl(®->pcr);
> + tmp |= PCR_PHY0_RESET_CLEAR;
> +
> + writel(tmp, ®->pcr);
> + udelay(100000);
you already explained why you need such a long delay. It is not bad to
add your explanation as comment here, so everyone knows your answer.
> +static void ax88783_halt(struct eth_device *dev)
> +{
> + unsigned int tmp;
> + struct ax88783_reg *reg = (struct ax88783_reg *)dev->iobase;
> + tmp = readl(®->pcr);
> + writel((tmp | PCR_LOOP_BACK), ®->pcr);
> +}
next prev parent reply other threads:[~2011-02-02 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Joe Xue>
2011-01-29 2:03 ` [U-Boot] [PATCH] Add support for AX88183 ethernet chip Joe Xue
2011-01-30 18:42 ` stefano babic
2011-01-31 17:35 ` [U-Boot] [PATCH] Add support for ASIX's AX88783 " Joe Xue
2011-01-31 17:42 ` Joe Xue
2011-02-02 18:02 ` Stefano Babic [this message]
2011-02-04 14:47 ` Joe XUE
2011-02-04 15:23 ` Stefano Babic
2011-02-04 15:59 ` Wolfgang Denk
2011-02-04 19:56 ` [U-Boot] [PATCH] Add support Asix's AX88783 ethernet chip v1.00 Joe Xue
2011-02-15 8:15 ` Mike Frysinger
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=4D499C23.40500@denx.de \
--to=sbabic@denx.de \
--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