From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: claudiu beznea <claudiu.beznea@tuxon.dev>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<yoshihiro.shimoda.uh@renesas.com>,
<wsa+renesas@sang-engineering.com>,
<mitsuhiro.kimura.kc@renesas.com>
Cc: <netdev@vger.kernel.org>, <linux-renesas-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH net v2 1/1] net: ravb: Wait for operation mode to be applied
Date: Thu, 28 Dec 2023 22:07:30 +0300 [thread overview]
Message-ID: <9ebf96fb-c07a-8269-e5cd-0e71110941dd@omp.ru> (raw)
In-Reply-To: <d5448a91-a4d8-444d-9f96-083049b1e33e@tuxon.dev>
On 12/27/23 1:10 PM, claudiu beznea 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 by HW when the operating mode change
>>> request is processed. To comply with this check CSR.OPS before proceeding.
>>>
>>> Commit introduces ravb_set_opmode() that does all the necessities for
>>> setting the operating mode (set DMA.CCC and wait for CSR.OPS) and call it
>>> where needed. This should comply with all the HW manuals requirements as
>>> different manual variants specify that different modes need to be checked
>>> in CSR.OPS when setting DMA.CCC.
>>>
>>> Fixes: c156633f1353 ("Renesas Ethernet AVB driver proper")
>>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>> ---
>>> drivers/net/ethernet/renesas/ravb_main.c | 52 ++++++++++++++----------
>>> 1 file changed, 31 insertions(+), 21 deletions(-)
>>>
>>> diff --git a/drivers/net/ethernet/renesas/ravb_main.c b/drivers/net/ethernet/renesas/ravb_main.c
>>> index 664eda4b5a11..ae99d035a3b6 100644
>>> --- a/drivers/net/ethernet/renesas/ravb_main.c
>>> +++ b/drivers/net/ethernet/renesas/ravb_main.c
>>> @@ -66,14 +66,15 @@ int ravb_wait(struct net_device *ndev, enum ravb_reg reg, u32 mask, u32 value)
>>> return -ETIMEDOUT;
>>> }
>>>
>>> -static int ravb_config(struct net_device *ndev)
>>> +static int ravb_set_opmode(struct net_device *ndev, u32 opmode)
>>
>> Since you pass the complete CCC register value below, you should
>> rather call the function ravb_set_ccc() and call the parameter opmode
>> ccc.
>
> This will be confusing. E.g., if renaming it ravb_set_ccc() one would
> expect to set any fields of CCC though this function but this is not true
> as ravb_modify() in this function masks only CCC_OPC. The call of:
>
> error = ravb_set_opmode(ndev, CCC_OPC_CONFIG | CCC_GAC | CCC_CSEL_HPB);
>
> bellow is just to comply with datasheet requirements, previous code and at
> the same time re-use this function.
How about the following then (ugly... but does the job):
/* Set operating mode */
if (opmode & ~CCC_OPC)
ravb_write(ndev, opmode, CCC);
else
ravb_modify(ndev, CCC, CCC_OPC, opmode);
Either that or just don't use ravb_set_opmode() when writing the whole
32-bit value below...
[...]
>>> @@ -2560,21 +2559,23 @@ static int ravb_set_gti(struct net_device *ndev)
[...]
>>
>>> /* Set CSEL value */
>>> ravb_modify(ndev, CCC, CCC_CSEL, CCC_CSEL_HPB);
>>> } else if (info->ccc_gac) {
>>> - ravb_modify(ndev, CCC, CCC_OPC, CCC_OPC_CONFIG |
>>> - CCC_GAC | CCC_CSEL_HPB);
>>> + error = ravb_set_opmode(ndev, CCC_OPC_CONFIG | CCC_GAC | CCC_CSEL_HPB);
... like this?
ravb_write(ndev, CCC_OPC_CONFIG | CCC_GAC | CCC_CSEL_HPB, CCC);
error = ravb_wait(ndev, CSR, CSR_OPS, CSR_OPS_CONFIG);
[...]
MBR, Sergey
next prev parent reply other threads:[~2023-12-28 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 11:35 [PATCH net v2 0/1] net: ravb: fixes for the ravb driver Claudiu
2023-12-22 11:35 ` [PATCH net v2 1/1] net: ravb: Wait for operation mode to be applied Claudiu
2023-12-23 19:39 ` Sergey Shtylyov
2023-12-27 10:10 ` claudiu beznea
2023-12-27 10:43 ` claudiu beznea
2023-12-28 19:07 ` Sergey Shtylyov [this message]
2023-12-29 15:07 ` claudiu beznea
2024-01-01 20:49 ` Sergey Shtylyov
2023-12-23 19:43 ` Sergey Shtylyov
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=9ebf96fb-c07a-8269-e5cd-0e71110941dd@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).