From: Amit Virdi <amit.virdi@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] net/designware: Consecutive writes to the same register to be avoided
Date: Mon, 11 Jun 2012 09:56:57 +0530 [thread overview]
Message-ID: <4FD57391.3060702@st.com> (raw)
In-Reply-To: <1339169212-2417-1-git-send-email-dinguyen@altera.com>
On 6/8/2012 8:56 PM, Dinh Nguyen wrote:
> This commit is an add-on to f6c4191f. There are a few registers where
> consecutive writes to the same location should be avoided or have a delay.
>
> According to Synopsys, here is a list of the registers and bit(s) where
> consecutive writes should be avoided or a delay is required:
>
> DMA Registers:
> Register 0 Bit 7
> Register 6 All bits except for 24, 16-13, 2-1.
>
> GMAC Registers:
> Registers 0-3 All bits
> Registers 6-7 All bits
> Register 10 All bits
> Register 11 All bits except for 5-6.
> Registers 16-47 All bits
> Register 48 All bits except for 18-16, 14.
> Register 448 Bit 4.
> Register 459 Bits 0-3.
>
> Reviewd-by: Matthew Gerlach<mgerlach@altera.com>
> Signed-off-by: Dinh Nguyen<dinguyen@altera.com>
> ---
> drivers/net/designware.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/designware.c b/drivers/net/designware.c
> index e8e669b..980b92f 100644
> --- a/drivers/net/designware.c
> +++ b/drivers/net/designware.c
> @@ -163,8 +163,8 @@ static int dw_eth_init(struct eth_device *dev, bd_t *bis)
> writel(FIXEDBURST | PRIORXTX_41 | BURST_16,
> &dma_p->busmode);
>
> - writel(FLUSHTXFIFO | readl(&dma_p->opmode),&dma_p->opmode);
> - writel(STOREFORWARD | TXSECONDFRAME,&dma_p->opmode);
> + writel(readl(&dma_p->opmode) | FLUSHTXFIFO | STOREFORWARD |
> + TXSECONDFRAME,&dma_p->opmode);
>
> conf = FRAMEBURSTENABLE | DISABLERXOWN;
>
Acked-by: Amit Virdi <amit.virdi@st.com>
next prev parent reply other threads:[~2012-06-11 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 15:26 [U-Boot] [PATCH v2] net/designware: Consecutive writes to the same register to be avoided Dinh Nguyen
2012-06-11 4:26 ` Amit Virdi [this message]
2012-07-11 18:27 ` Joe Hershberger
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=4FD57391.3060702@st.com \
--to=amit.virdi@st.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 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.