From: Justin Lai <justinlai0215@realtek.com>
To: Michal Kubiak <michal.kubiak@intel.com>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"horms@kernel.org" <horms@kernel.org>,
Ping-Ke Shih <pkshih@realtek.com>,
Larry Chiu <larry.chiu@realtek.com>
Subject: RE: [PATCH net v3 1/4] rtase: Refactor the rtase_check_mac_version_valid() function
Date: Tue, 19 Nov 2024 07:23:02 +0000 [thread overview]
Message-ID: <b55ab4efb8e74ecda3ce5c3b4dca2b12@realtek.com> (raw)
In-Reply-To: <ZzssJBOcb807PYSP@localhost.localdomain>
> On Mon, Nov 18, 2024 at 12:08:25PM +0800, Justin Lai wrote:
> > 1. Sets tp->hw_ver.
> > 2. Changes the return type from bool to int.
> > 3. Modify the error message for an invalid hardware version id.
>
> The commit message contains too many implementation details (that are quite
> obvious after studying the code), but there is no information about the actual
> problem the patch is fixing.
Thank you for your feedback. I will make the necessary adjustments to the
commit message.
>
> >
> > Fixes: a36e9f5cfe9e ("rtase: Add support for a pci table in this
> > module")
> > Signed-off-by: Justin Lai <justinlai0215@realtek.com>
> > ---
> > drivers/net/ethernet/realtek/rtase/rtase.h | 2 ++
> > .../net/ethernet/realtek/rtase/rtase_main.c | 22 +++++++++++--------
> > 2 files changed, 15 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/realtek/rtase/rtase.h
> > b/drivers/net/ethernet/realtek/rtase/rtase.h
> > index 583c33930f88..547c71937b01 100644
> > --- a/drivers/net/ethernet/realtek/rtase/rtase.h
> > +++ b/drivers/net/ethernet/realtek/rtase/rtase.h
> > @@ -327,6 +327,8 @@ struct rtase_private {
> > u16 int_nums;
> > u16 tx_int_mit;
> > u16 rx_int_mit;
> > +
> > + u32 hw_ver;
> > };
> >
> > #define RTASE_LSO_64K 64000
> > diff --git a/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > b/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > index f8777b7663d3..0c19c5645d53 100644
> > --- a/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > +++ b/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > @@ -1972,20 +1972,21 @@ static void rtase_init_software_variable(struct
> pci_dev *pdev,
> > tp->dev->max_mtu = RTASE_MAX_JUMBO_SIZE; }
> >
> > -static bool rtase_check_mac_version_valid(struct rtase_private *tp)
> > +static int rtase_check_mac_version_valid(struct rtase_private *tp)
> > {
> > - u32 hw_ver = rtase_r32(tp, RTASE_TX_CONFIG_0) &
> RTASE_HW_VER_MASK;
> > - bool known_ver = false;
> > + int ret = -ENODEV;
> >
> > - switch (hw_ver) {
> > + tp->hw_ver = rtase_r32(tp, RTASE_TX_CONFIG_0) &
> > + RTASE_HW_VER_MASK;
> > +
> > + switch (tp->hw_ver) {
> > case 0x00800000:
> > case 0x04000000:
> > case 0x04800000:
> > - known_ver = true;
> > + ret = 0;
> > break;
> > }
> >
> > - return known_ver;
> > + return ret;
> > }
> >
> > static int rtase_init_board(struct pci_dev *pdev, struct net_device
> > **dev_out, @@ -2105,9 +2106,12 @@ static int rtase_init_one(struct
> pci_dev *pdev,
> > tp->pdev = pdev;
> >
> > /* identify chip attached to board */
> > - if (!rtase_check_mac_version_valid(tp))
> > - return dev_err_probe(&pdev->dev, -ENODEV,
> > - "unknown chip version, contact
> rtase maintainers (see MAINTAINERS file)\n");
> > + ret = rtase_check_mac_version_valid(tp);
> > + if (ret != 0) {
>
> Maybe "if (!ret)" would be more readable?
Since this function has several instances of this issue that need to be
addressed, I will create a separate patch to make the necessary
corrections.
>
> > + dev_err(&pdev->dev,
> > + "unknown chip version: 0x%08x, contact rtase
> maintainers (see MAINTAINERS file)\n",
> > + tp->hw_ver);
> > + }
>
> Also, is it OK to perform further initialization steps although we're getting an
> error here? Could you please provide more details in the commit message?
In [PATCH net v3 3/4] rtase: Corrects error handling of the
rtase_check_mac_version_valid(), it can be observed how errors are
handled in case of an issue.
> >
> > rtase_init_software_variable(pdev, tp);
> > rtase_init_hardware(tp);
> > --
> > 2.34.1
> >
> >
>
> Thanks,
> Michal
next prev parent reply other threads:[~2024-11-19 7:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 4:08 [PATCH net v3 0/4] Correcting switch hardware versions and reported speeds Justin Lai
2024-11-18 4:08 ` [PATCH net v3 1/4] rtase: Refactor the rtase_check_mac_version_valid() function Justin Lai
2024-11-18 11:59 ` Michal Kubiak
2024-11-19 7:23 ` Justin Lai [this message]
2024-11-18 4:08 ` [PATCH net v3 2/4] rtase: Correct the speed for RTL907XD-V1 Justin Lai
2024-11-18 12:09 ` Michal Kubiak
2024-11-19 7:23 ` Justin Lai
2024-11-19 11:42 ` Michal Kubiak
2024-11-20 6:40 ` Justin Lai
2024-11-18 4:08 ` [PATCH net v3 3/4] rtase: Corrects error handling of the rtase_check_mac_version_valid() Justin Lai
2024-11-18 4:08 ` [PATCH net v3 4/4] rtase: Add defines for hardware version id Justin Lai
2024-11-18 11:15 ` Michal Kubiak
2024-11-19 7:22 ` Justin Lai
2024-11-19 11:28 ` Michal Kubiak
2024-11-20 6:40 ` Justin Lai
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=b55ab4efb8e74ecda3ce5c3b4dca2b12@realtek.com \
--to=justinlai0215@realtek.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkshih@realtek.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).