[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240102110116.4005187-1-claudiu.beznea.uj@bp.renesas.com>
Date: Tue, 2 Jan 2024 13:01:15 +0200
From: Claudiu <claudiu.beznea@...on.dev>
To: s.shtylyov@....ru,
davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com
Cc: mitsuhiro.kimura.kc@...esas.com,
netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org,
claudiu.beznea@...on.dev,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Subject: [PATCH net v3 0/1] net: ravb: fixes for the ravb driver
From: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Hi,
Series adds one fix for the ravb driver to wait for the operating
mode to be applied by hardware before proceeding.
Thank you,
Claudiu Beznea
Changes in v3:
- s/csr_opmode/csr_ops in ravb_set_opmode()
- mask opmode with CCC_OPC when retrieveing csr_ops
- in ravb_set_opmode() updated modify mask passed to ravb_modify() to
include GAC and CSEL bits if these are part of opmode
- s/failed to switch device to config mode/failed to switch device to
requested mode/ in ravb_set_opmode()
- s/operation/operating in the title of patch 1/1
Changes in v2:
- dropped patch 2/2 from v1 ("net: ravb: Check that GTI loading request is
done")
- kept a single "Fixes" entry in commit description
- updated commit description for patch 1/1
- introduce 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 different modes need to be checked in
CSR.OPS when setting DMA.CCC.
Claudiu Beznea (1):
net: ravb: Wait for operation mode to be applied
drivers/net/ethernet/renesas/ravb_main.c | 61 +++++++++++++++---------
1 file changed, 38 insertions(+), 23 deletions(-)
--
2.39.2
Powered by blists - more mailing lists