On 1/24/2022 6:51 AM, Ilpo Järvinen wrote:
On Thu, 13 Jan 2022, Ricardo Martinez wrote:
From: Haijun Liu <haijun.liu@xxxxxxxxxxxx>
Registers the t7xx device driver with the kernel. Setup all the core
components: PCIe layer, Modem Host Cross Core Interface (MHCCIF),
modem control operations, modem state machine, and build
infrastructure.
* PCIe layer code implements driver probe and removal.
* MHCCIF provides interrupt channels to communicate events
such as handshake, PM and port enumeration.
* Modem control implements the entry point for modem init,
reset and exit.
* The modem status monitor is a state machine used by modem control
to complete initialization and stop. It is used also to propagate
exception events reported by other components.
Signed-off-by: Haijun Liu <haijun.liu@xxxxxxxxxxxx>
Signed-off-by: Chandrashekar Devegowda <chandrashekar.devegowda@xxxxxxxxx>
Co-developed-by: Ricardo Martinez <ricardo.martinez@xxxxxxxxxxxxxxx>
Signed-off-by: Ricardo Martinez <ricardo.martinez@xxxxxxxxxxxxxxx>
---
Some states in t7xx_common.h (MD_STATE_...) would logically belong to this
patch instead of 02/. ...I think they were initally here but got moved
with t7xx_skb_data_area_size(). And there was also things clearly related
to 05/ in t7xx_common.h (at least CTL_ID_*).
Originally, 02 and 03 were going to be part of the same "Core
functionality" patch,
the only reason for splitting it was to make that core patch smaller.
The result is that
02 uses code defined at 03, note that compilation is enabled at 03.
Will merge 02 and 03 in the next version, also clean t7xx_common.h from
definitions
not used.
...
+int t7xx_fsm_append_cmd(struct t7xx_fsm_ctl *ctl, enum t7xx_fsm_cmd_state cmd_id, unsigned int flag)
No callsite in this patch seems to care about the error code, is it ok?
Even though there's no recovery path (like retry) for
t7xx_fsm_append_cmd() failures, it makes sense to
propagate the error instead of ignoring it, will add that in the next
version.
E.g.:
+int t7xx_md_init(struct t7xx_pci_dev *t7xx_dev)
+{
...
If this returns an error, does it mean init/probe stalls? Or is there
some backup to restart?
An error here will cause probe to fail, there's no recovery path for this.
