From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Sergey Shtylyov <s.shtylyov@omp.ru>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.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-next 4/5] net: ravb: Do not apply RX checksum settings to hardware if the interface is down
Date: Thu, 8 Feb 2024 18:11:35 +0200 [thread overview]
Message-ID: <cf24ed20-c2c1-4f36-a747-e01f5a36b61d@tuxon.dev> (raw)
In-Reply-To: <82a95cae-29bc-06c1-0fab-5fa6302b4654@omp.ru>
On 07.02.2024 22:50, Sergey Shtylyov wrote:
> On 2/7/24 3:07 PM, Claudiu wrote:
>
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> Do not apply the RX checksum settings to hardware if the interface is down.
>> In case runtime PM is enabled, and while the interface is down, the IP will
>> be in reset mode (as for some platforms disabling the clocks will switch
>> the IP to reset mode, which will lead to losing registers content) and
>
> The register contents? I thought I'd pointed out all of these...
>
>> applying settings in reset mode is not an option. Instead, cache the RX
>> checksum settings and apply them in ravb_open() through ravb_emac_init().
>> This has been solved by introducing pm_runtime_active() check. The device
>> runtime PM usage counter has been incremented to avoid disabling the device
>> clocks while the check is in progress (if any).
>>
>> Commit prepares for the addition of runtime PM.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>
> I'm afraid such check now needs to be added to ravb_set_features_gbeth()
> that's populated by Biju Das' checksum patches (which I've already ACKed)...
Yes, it's on my radar. I'll check it and update it (if any) in the next
version.
Thank you,
Claudiu Beznea
>
> [...]
>
> MBR, Sergey
next prev parent reply other threads:[~2024-02-08 16:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 12:07 [PATCH net-next 0/5] net: ravb: Add runtime PM support (part 2) Claudiu
2024-02-07 12:07 ` [PATCH net-next 1/5] net: ravb: Get rid of the temporary variable irq Claudiu
2024-02-08 20:43 ` Sergey Shtylyov
2024-02-09 5:48 ` claudiu beznea
2024-02-09 19:43 ` Sergey Shtylyov
2024-02-08 20:44 ` Sergey Shtylyov
2024-02-07 12:07 ` [PATCH net-next 2/5] net: ravb: Keep the reverse order of operations in ravb_close() Claudiu
2024-02-07 12:07 ` [PATCH net-next 3/5] net: ravb: Return cached statistics if the interface is down Claudiu
2024-02-07 20:18 ` Sergey Shtylyov
2024-02-07 12:07 ` [PATCH net-next 4/5] net: ravb: Do not apply RX checksum settings to hardware " Claudiu
2024-02-07 20:50 ` Sergey Shtylyov
2024-02-08 8:09 ` Biju Das
2024-02-08 9:16 ` Biju Das
2024-02-08 16:11 ` claudiu beznea [this message]
2024-02-07 12:07 ` [PATCH net-next 5/5] net: ravb: Add runtime PM support Claudiu
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=cf24ed20-c2c1-4f36-a747-e01f5a36b61d@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=claudiu.beznea.uj@bp.renesas.com \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
/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®