From: Leon Romanovsky <leon@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: Veerasenareddy Burru <vburru@marvell.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
aayarekar@marvell.com, sedara@marvell.com, sburla@marvell.com,
linux-doc@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v3 1/7] octeon_ep: defer probe if firmware not ready
Date: Wed, 15 Feb 2023 13:43:13 +0200 [thread overview]
Message-ID: <Y+zFUUhogjJyp58e@unreal> (raw)
In-Reply-To: <Y+vFlfakHj33DEkt@boxer>
On Tue, Feb 14, 2023 at 06:32:05PM +0100, Maciej Fijalkowski wrote:
> On Mon, Feb 13, 2023 at 09:14:16PM -0800, Veerasenareddy Burru wrote:
> > Defer probe if firmware is not ready for device usage.
> >
> > Signed-off-by: Veerasenareddy Burru <vburru@marvell.com>
> > Signed-off-by: Abhijit Ayarekar <aayarekar@marvell.com>
> > Signed-off-by: Satananda Burla <sburla@marvell.com>
> > ---
> > v2 -> v3:
> > * fix review comments
> > https://lore.kernel.org/all/Y4chWyR6qTlptkTE@unreal/
> > - change get_fw_ready_status() to return bool
> > - fix the success oriented flow while looking for
> > PCI extended capability
> >
> > v1 -> v2:
> > * was scheduling workqueue task to wait for firmware ready,
> > to probe/initialize the device.
> > * now, removed the workqueue task; the probe returns EPROBE_DEFER,
> > if firmware is not ready.
> > * removed device status oct->status, as it is not required with the
> > modified implementation.
> >
> > .../ethernet/marvell/octeon_ep/octep_main.c | 26 +++++++++++++++++++
> > 1 file changed, 26 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/marvell/octeon_ep/octep_main.c b/drivers/net/ethernet/marvell/octeon_ep/octep_main.c
> > index 5a898fb88e37..5620df4c6d55 100644
> > --- a/drivers/net/ethernet/marvell/octeon_ep/octep_main.c
> > +++ b/drivers/net/ethernet/marvell/octeon_ep/octep_main.c
> > @@ -1017,6 +1017,26 @@ static void octep_device_cleanup(struct octep_device *oct)
> > oct->conf = NULL;
> > }
> >
> > +static bool get_fw_ready_status(struct pci_dev *pdev)
> > +{
> > + u32 pos = 0;
> > + u16 vsec_id;
> > + u8 status;
> > +
> > + while ((pos = pci_find_next_ext_capability(pdev, pos,
> > + PCI_EXT_CAP_ID_VNDR))) {
> > + pci_read_config_word(pdev, pos + 4, &vsec_id);
> > +#define FW_STATUS_VSEC_ID 0xA3
> > + if (vsec_id != FW_STATUS_VSEC_ID)
> > + continue;
> > +
> > + pci_read_config_byte(pdev, (pos + 8), &status);
> > + dev_info(&pdev->dev, "Firmware ready status = %u\n", status);
> > + return status ? true : false;
>
> nit:
>
> return !!status;
"return status;" is enough, there is no need in "!!".
Thanks
next prev parent reply other threads:[~2023-02-15 11:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 5:14 [PATCH net-next v3 0/7] octeon_ep: deferred probe and mailbox Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 1/7] octeon_ep: defer probe if firmware not ready Veerasenareddy Burru
2023-02-14 17:32 ` Maciej Fijalkowski
2023-02-15 11:43 ` Leon Romanovsky [this message]
2023-02-17 8:21 ` [EXT] " Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 2/7] octeon_ep: poll for control messages Veerasenareddy Burru
2023-02-14 17:42 ` Maciej Fijalkowski
2023-02-17 8:25 ` [EXT] " Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 3/7] octeon_ep: control mailbox for multiple PFs Veerasenareddy Burru
2023-02-14 17:49 ` Maciej Fijalkowski
2023-02-17 17:15 ` [EXT] " Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 4/7] octeon_ep: enhance control mailbox for VF support Veerasenareddy Burru
2023-02-15 15:55 ` Maciej Fijalkowski
2023-03-22 7:24 ` [EXT] " Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 5/7] octeon_ep: support asynchronous notifications Veerasenareddy Burru
2023-02-15 16:36 ` Maciej Fijalkowski
2023-03-22 7:26 ` [EXT] " Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 6/7] octeon_ep: control mbox support for VF stats and link info Veerasenareddy Burru
2023-02-14 5:14 ` [PATCH net-next v3 7/7] octeon_ep: add heartbeat monitor Veerasenareddy Burru
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=Y+zFUUhogjJyp58e@unreal \
--to=leon@kernel.org \
--cc=aayarekar@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=vburru@marvell.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).