From: Beniamino Galvani <b.galvani@gmail.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: edgar.iglesias@gmail.com, nathan.rossi@xilinx.com,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH microblaze v1 1/1] net: xilinx_axienet.c: Add phy soft reset bit clearing
Date: Wed, 9 Apr 2014 23:02:18 +0200 [thread overview]
Message-ID: <20140409210217.GB794@gmail.com> (raw)
In-Reply-To: <92818a0dc14afd5bc49ea630f1a12b13b909c71d.1397008011.git.peter.crosthwaite@xilinx.com>
On Tue, Apr 08, 2014 at 06:52:39PM -0700, Peter Crosthwaite wrote:
> From: Nathan Rossi <nathan.rossi@xilinx.com>
>
> Clear the BMCR Reset when writing to registers.
>
> Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com>
> [ PC:
> * Trivial style fixes to commit message
> ]
> Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> ---
>
> hw/net/xilinx_axienet.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/hw/net/xilinx_axienet.c b/hw/net/xilinx_axienet.c
> index 839d97c..0f485a0 100644
> --- a/hw/net/xilinx_axienet.c
> +++ b/hw/net/xilinx_axienet.c
> @@ -142,6 +142,9 @@ tdk_write(struct PHY *phy, unsigned int req, unsigned int data)
> phy->regs[regnum] = data;
> break;
> }
> +
> + /* Unconditionally clear regs[BMCR][BMCR_RESET] */
> + phy->regs[0] &= ~0x8000;
> }
>
> static void
> --
Reviewed-by: Beniamino Galvani <b.galvani@gmail.com>
Ideally we should also restore default values of registers after a
reset, but probably it is not required for the guest to operate
properly.
Beniamino
prev parent reply other threads:[~2014-04-09 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 1:52 [Qemu-devel] [PATCH microblaze v1 1/1] net: xilinx_axienet.c: Add phy soft reset bit clearing Peter Crosthwaite
2014-04-09 21:02 ` Beniamino Galvani [this message]
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=20140409210217.GB794@gmail.com \
--to=b.galvani@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=nathan.rossi@xilinx.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.