From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Claudiu <claudiu.beznea@tuxon.dev>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<claudiu.beznea.uj@bp.renesas.com>,
<yoshihiro.shimoda.uh@renesas.com>,
<wsa+renesas@sang-engineering.com>,
<niklas.soderlund+renesas@ragnatech.se>,
<biju.das.jz@bp.renesas.com>,
<prabhakar.mahadev-lad.rj@bp.renesas.com>,
<mitsuhiro.kimura.kc@renesas.com>, <geert+renesas@glider.be>
Cc: <netdev@vger.kernel.org>, <linux-renesas-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net 1/2] net: ravb: Wait for operation mode to be applied
Date: Thu, 14 Dec 2023 22:41:53 +0300 [thread overview]
Message-ID: <d08dbbd4-2e63-c436-6935-df68c291bf75@omp.ru> (raw)
In-Reply-To: <20231214113137.2450292-2-claudiu.beznea.uj@bp.renesas.com>
resetOn 12/14/23 2:31 PM, Claudiu wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> CSR.OPS bits specify the current operating mode and (according to
> documentation) they are updated when the operating mode change request
> is processed. Thus, check CSR.OPS before proceeding.
The manuals I have indeed say we need to check CSR.OPS... But we only
need to wait iff we transfer from the operation mode to the config mode...
> Fixes: 568b3ce7a8ef ("ravb: factor out register bit twiddling code")
> Fixes: 0184165b2f42 ("ravb: add sleep PM suspend/resume support")
> Fixes: 7e09a052dc4e ("ravb: Exclude gPTP feature support for RZ/G2L")
> Fixes: 3e3d647715d4 ("ravb: add wake-on-lan support via magic packet")
> Fixes: c156633f1353 ("Renesas Ethernet AVB driver proper")
Hm, that long list does look weird...
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> ---
> drivers/net/ethernet/renesas/ravb_main.c | 47 ++++++++++++++++++++----
> 1 file changed, 39 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/ethernet/renesas/ravb_main.c b/drivers/net/ethernet/renesas/ravb_main.c
> index 9178f6d60e74..ce95eb5af354 100644
> --- a/drivers/net/ethernet/renesas/ravb_main.c
> +++ b/drivers/net/ethernet/renesas/ravb_main.c
> @@ -683,8 +683,11 @@ static int ravb_dmac_init(struct net_device *ndev)
>
> /* Setting the control will start the AVB-DMAC process. */
> ravb_modify(ndev, CCC, CCC_OPC, CCC_OPC_OPERATION);
> + error = ravb_wait(ndev, CSR, CSR_OPS, CSR_OPS_OPERATION);
> + if (error)
> + netdev_err(ndev, "failed to switch device to operation mode\n");
It doesn't look like ravb_wait() is needed here...
And besides, this pattern seems repetitive and worth factoring out into
a single function.
[...]
> @@ -1744,6 +1747,18 @@ static inline int ravb_hook_irq(unsigned int irq, irq_handler_t handler,
> return error;
> }
>
> +static int ravb_set_reset_mode(struct net_device *ndev)
> +{
> + int error;
> +
> + ravb_write(ndev, CCC_OPC_RESET, CCC);
> + error = ravb_wait(ndev, CSR, CSR_OPS, CSR_OPS_RESET);
> + if (error)
> + netdev_err(ndev, "failed to switch device to reset mode\n");
> +
> + return error;
> +}
> +
Again, ravb_wait() call doesn't seem necessary here...
[...]
MBR, Sergey
next prev parent reply other threads:[~2023-12-14 19:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 11:31 [PATCH net 0/2] net: ravb: fixes for the ravb driver Claudiu
2023-12-14 11:31 ` [PATCH net 1/2] net: ravb: Wait for operation mode to be applied Claudiu
2023-12-14 12:11 ` Niklas Söderlund
2023-12-14 12:25 ` claudiu beznea
2023-12-14 12:39 ` Niklas Söderlund
2023-12-14 12:57 ` claudiu beznea
2023-12-14 19:41 ` Sergey Shtylyov [this message]
2023-12-15 10:04 ` claudiu beznea
2023-12-19 16:49 ` Sergey Shtylyov
2023-12-20 11:27 ` claudiu beznea
2023-12-14 11:31 ` [PATCH net 2/2] net: ravb: Check that GTI loading request is done Claudiu
2023-12-14 12:33 ` Niklas Söderlund
2023-12-14 13:02 ` claudiu beznea
2023-12-14 20:22 ` Sergey Shtylyov
2023-12-15 10:13 ` claudiu beznea
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=d08dbbd4-2e63-c436-6935-df68c291bf75@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mitsuhiro.kimura.kc@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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
all inboxes | Powered by JetHome®