linux-toradex.git/include/linux/pds, branch v6.4-rc1

pds_core: publish events to the clients

2023-04-21T07:29:13+00:00

When the Core device gets an event from the device, or notices
the device FW to be up or down, it needs to send those events
on to the clients that have an event handler.  Add the code to
pass along the events to the clients.

The entry points pdsc_register_notify() and pdsc_unregister_notify()
are EXPORTed for other drivers that want to listen for these events.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: add the aux client API

2023-04-21T07:29:13+00:00

Add the client API operations for running adminq commands.
The core registers the client with the FW, then the client
has a context for requesting adminq services.  We expect
to add additional operations for other clients, including
requesting additional private adminqs and IRQs, but don't have
the need yet.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: add auxiliary_bus devices

2023-04-21T07:29:13+00:00

An auxiliary_bus device is created for each vDPA type VF at VF
probe and destroyed at VF remove.  The aux device name comes
from the driver name + VIF type + the unique id assigned at PCI
probe.  The VFs are always removed on PF remove, so there should
be no issues with VFs trying to access missing PF structures.

The auxiliary_device names will look like "pds_core.vDPA.nn"
where 'nn' is the VF's uid.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: set up the VIF definitions and defaults

2023-04-21T07:29:13+00:00

The Virtual Interfaces (VIFs) supported by the DSC's
configuration (vDPA, Eth, RDMA, etc) are reported in the
dev_ident struct and made visible in debugfs.  At this point
only vDPA is supported in this driver so we only setup
devices for that feature.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: Add adminq processing and commands

2023-04-21T07:29:12+00:00

Add the service routines for submitting and processing
the adminq messages and for handling notifyq events.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: set up device and adminq

2023-04-21T07:29:12+00:00

Set up the basic adminq and notifyq queue structures.  These are
used mostly by the client drivers for feature configuration.
These are essentially the same adminq and notifyq as in the
ionic driver.

Part of this includes querying for device identity and FW
information, so we can make that available to devlink dev info.

  $ devlink dev info pci/0000:b5:00.0
  pci/0000:b5:00.0:
    driver pds_core
    serial_number FLM18420073
    versions:
        fixed:
          asic.id 0x0
          asic.rev 0x0
        running:
          fw 1.51.0-73
        stored:
          fw.goldfw 1.15.9-C-22
          fw.mainfwa 1.60.0-73
          fw.mainfwb 1.60.0-57

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: add devcmd device interfaces

2023-04-21T07:29:12+00:00

The devcmd interface is the basic connection to the device through the
PCI BAR for low level identification and command services.  This does
the early device initialization and finds the identity data, and adds
devcmd routines to be used by later driver bits.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller

pds_core: initial framework for pds_core PF driver

2023-04-21T07:29:12+00:00

This is the initial PCI driver framework for the new pds_core device
driver and its family of devices.  This does the very basics of
registering for the new PF PCI device 1dd8:100c, setting up debugfs
entries, and registering with devlink.

Signed-off-by: Shannon Nelson 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller