netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Dept-GELinuxNICDev@cavium.com,
	rasesh.mody@cavium.com, harish.patil@cavium.com,
	frank@undermydesk.org, jsr@dex.edzone.net, pmenzel@molgen.mpg.de,
	jroedel@suse.de, dyoung@redhat.com
Subject: Re: [PATCH 0/2] bnx2: Hard reset bnx2 chip at probe stage
Date: Fri, 11 Nov 2016 22:02:05 +0800	[thread overview]
Message-ID: <20161111140205.GD15325@x1> (raw)
In-Reply-To: <1478871995-29652-1-git-send-email-bhe@redhat.com>

On 11/11/16 at 09:46pm, Baoquan He wrote:
> Hi bnx2 experts,
> 
> In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
> firmware requesting code was moved from open stage to probe stage.
> The reason is in kdump kernel hardware iommu need device be reset in
> driver probe stage, otherwise those in-flight DMA from 1st kernel
> will continue going and look up into the newly created io-page tables.
> So we need reset device to stop in-flight DMA as early as possibe.
> 
> But with commit 3e1be7a merged, people reported their bnx2 driver init
> failed because of failed firmware loading. After discussion, it's found
> that they built bnx2 driver into kernel, and that makes probe function
> bnx2_init_one be called in do_initcalls(). But at this time the initramfs
> has not been uncompressed yet and mounted, kernel can't detect firmware.
> 
> So there's only one way to cover both. Try to hard reset the bnx2 device
> at probe stage, without involving firmware issues. I tried to add function
> bnx2_hard_reset_chip() to do this and it's only called in kdump kernel.
> The thing is I am not quite familiar with bnx2 chip spec, just abstract
> code from bnx2_reset_chip, the testing result is good.

Here I changed to send BNX2_MISC_COMMAND_HD_RESET in BNX2_CHIP_5709
case.

> 
> Any suggestions are welcomed and much appreciated!
> 
> Baoquan He (2):
>   Revert "bnx2: Reset device during driver initialization"
>   bnx2: Hard reset bnx2 chip at probe stage
> 
>  drivers/net/ethernet/broadcom/bnx2.c | 70 +++++++++++++++++++++++++++++++++---
>  1 file changed, 65 insertions(+), 5 deletions(-)
> 
> -- 
> 2.5.5
> 

  parent reply	other threads:[~2016-11-11 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 13:46 [PATCH 0/2] bnx2: Hard reset bnx2 chip at probe stage Baoquan He
2016-11-11 13:46 ` [PATCH 1/2] Revert "bnx2: Reset device during driver initialization" Baoquan He
2016-11-11 13:51   ` Paul Menzel
2016-11-11 13:46 ` [PATCH 2/2] bnx2: Hard reset bnx2 chip at probe stage Baoquan He
2016-11-13  4:15   ` [PATCH v2 2/2] bnx2: Wait for in-flight DMA to complete " Baoquan He
2016-11-13  4:40     ` David Miller
2016-11-13  4:54       ` Baoquan He
2016-11-11 14:02 ` Baoquan He [this message]
2016-11-11 17:37   ` [PATCH 0/2] bnx2: Hard reset bnx2 chip " Michael Chan
2016-11-13  4:10     ` Baoquan He

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=20161111140205.GD15325@x1 \
    --to=bhe@redhat.com \
    --cc=Dept-GELinuxNICDev@cavium.com \
    --cc=dyoung@redhat.com \
    --cc=frank@undermydesk.org \
    --cc=harish.patil@cavium.com \
    --cc=jroedel@suse.de \
    --cc=jsr@dex.edzone.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=rasesh.mody@cavium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).