2011-10-20 21:52:46 +07:00
|
|
|
/*
|
|
|
|
* Remote Processor Framework
|
|
|
|
*
|
|
|
|
* Copyright(c) 2011 Texas Instruments, Inc.
|
|
|
|
* Copyright(c) 2011 Google, Inc.
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
*
|
|
|
|
* * Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* * Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in
|
|
|
|
* the documentation and/or other materials provided with the
|
|
|
|
* distribution.
|
|
|
|
* * Neither the name Texas Instruments nor the names of its
|
|
|
|
* contributors may be used to endorse or promote products derived
|
|
|
|
* from this software without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
|
|
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
* OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
|
|
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef REMOTEPROC_H
|
|
|
|
#define REMOTEPROC_H
|
|
|
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/mutex.h>
|
|
|
|
#include <linux/virtio.h>
|
|
|
|
#include <linux/completion.h>
|
2012-02-14 04:30:39 +07:00
|
|
|
#include <linux/idr.h>
|
2015-05-23 03:45:27 +07:00
|
|
|
#include <linux/of.h>
|
2011-10-20 21:52:46 +07:00
|
|
|
|
|
|
|
/**
|
2012-02-02 02:56:16 +07:00
|
|
|
* struct resource_table - firmware resource table header
|
|
|
|
* @ver: version number
|
|
|
|
* @num: number of resource entries
|
|
|
|
* @reserved: reserved (must be zero)
|
|
|
|
* @offset: array of offsets pointing at the various resource entries
|
2011-10-20 21:52:46 +07:00
|
|
|
*
|
2012-02-02 02:56:16 +07:00
|
|
|
* A resource table is essentially a list of system resources required
|
|
|
|
* by the remote processor. It may also include configuration entries.
|
|
|
|
* If needed, the remote processor firmware should contain this table
|
|
|
|
* as a dedicated ".resource_table" ELF section.
|
2011-10-20 21:52:46 +07:00
|
|
|
*
|
|
|
|
* Some resources entries are mere announcements, where the host is informed
|
|
|
|
* of specific remoteproc configuration. Other entries require the host to
|
2012-02-02 02:56:16 +07:00
|
|
|
* do something (e.g. allocate a system resource). Sometimes a negotiation
|
|
|
|
* is expected, where the firmware requests a resource, and once allocated,
|
|
|
|
* the host should provide back its details (e.g. address of an allocated
|
|
|
|
* memory region).
|
|
|
|
*
|
|
|
|
* The header of the resource table, as expressed by this structure,
|
|
|
|
* contains a version number (should we need to change this format in the
|
|
|
|
* future), the number of available resource entries, and their offsets
|
|
|
|
* in the table.
|
|
|
|
*
|
|
|
|
* Immediately following this header are the resource entries themselves,
|
|
|
|
* each of which begins with a resource entry header (as described below).
|
|
|
|
*/
|
|
|
|
struct resource_table {
|
|
|
|
u32 ver;
|
|
|
|
u32 num;
|
|
|
|
u32 reserved[2];
|
2020-05-08 02:19:43 +07:00
|
|
|
u32 offset[];
|
2012-02-02 02:56:16 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct fw_rsc_hdr - firmware resource entry header
|
|
|
|
* @type: resource type
|
|
|
|
* @data: resource data
|
|
|
|
*
|
|
|
|
* Every resource entry begins with a 'struct fw_rsc_hdr' header providing
|
|
|
|
* its @type. The content of the entry itself will immediately follow
|
|
|
|
* this header, and it should be parsed according to the resource type.
|
2011-10-20 21:52:46 +07:00
|
|
|
*/
|
2012-02-02 02:56:16 +07:00
|
|
|
struct fw_rsc_hdr {
|
2011-10-20 21:52:46 +07:00
|
|
|
u32 type;
|
2020-05-08 02:19:43 +07:00
|
|
|
u8 data[];
|
2011-10-20 21:52:46 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* enum fw_resource_type - types of resource entries
|
|
|
|
*
|
|
|
|
* @RSC_CARVEOUT: request for allocation of a physically contiguous
|
|
|
|
* memory region.
|
|
|
|
* @RSC_DEVMEM: request to iommu_map a memory-based peripheral.
|
|
|
|
* @RSC_TRACE: announces the availability of a trace buffer into which
|
2012-02-02 02:56:16 +07:00
|
|
|
* the remote processor will be writing logs.
|
|
|
|
* @RSC_VDEV: declare support for a virtio device, and serve as its
|
|
|
|
* virtio header.
|
2019-06-17 19:57:30 +07:00
|
|
|
* @RSC_LAST: just keep this one at the end of standard resources
|
|
|
|
* @RSC_VENDOR_START: start of the vendor specific resource types range
|
|
|
|
* @RSC_VENDOR_END: end of the vendor specific resource types range
|
2011-10-20 21:52:46 +07:00
|
|
|
*
|
2012-02-02 02:56:16 +07:00
|
|
|
* For more details regarding a specific resource type, please see its
|
|
|
|
* dedicated structure below.
|
2012-01-31 21:07:27 +07:00
|
|
|
*
|
|
|
|
* Please note that these values are used as indices to the rproc_handle_rsc
|
|
|
|
* lookup table, so please keep them sane. Moreover, @RSC_LAST is used to
|
|
|
|
* check the validity of an index before the lookup table is accessed, so
|
|
|
|
* please update it as needed.
|
2011-10-20 21:52:46 +07:00
|
|
|
*/
|
|
|
|
enum fw_resource_type {
|
2019-06-17 19:57:30 +07:00
|
|
|
RSC_CARVEOUT = 0,
|
|
|
|
RSC_DEVMEM = 1,
|
|
|
|
RSC_TRACE = 2,
|
|
|
|
RSC_VDEV = 3,
|
|
|
|
RSC_LAST = 4,
|
|
|
|
RSC_VENDOR_START = 128,
|
|
|
|
RSC_VENDOR_END = 512,
|
2011-10-20 21:52:46 +07:00
|
|
|
};
|
|
|
|
|
2016-09-06 14:39:42 +07:00
|
|
|
#define FW_RSC_ADDR_ANY (-1)
|
2012-02-02 02:56:16 +07:00
|
|
|
|
|
|
|
/**
|
|
|
|
* struct fw_rsc_carveout - physically contiguous memory request
|
|
|
|
* @da: device address
|
|
|
|
* @pa: physical address
|
|
|
|
* @len: length (in bytes)
|
|
|
|
* @flags: iommu protection flags
|
|
|
|
* @reserved: reserved (must be zero)
|
|
|
|
* @name: human-readable name of the requested memory region
|
|
|
|
*
|
|
|
|
* This resource entry requests the host to allocate a physically contiguous
|
|
|
|
* memory region.
|
|
|
|
*
|
|
|
|
* These request entries should precede other firmware resource entries,
|
|
|
|
* as other entries might request placing other data objects inside
|
|
|
|
* these memory regions (e.g. data/code segments, trace resource entries, ...).
|
|
|
|
*
|
|
|
|
* Allocating memory this way helps utilizing the reserved physical memory
|
|
|
|
* (e.g. CMA) more efficiently, and also minimizes the number of TLB entries
|
|
|
|
* needed to map it (in case @rproc is using an IOMMU). Reducing the TLB
|
|
|
|
* pressure is important; it may have a substantial impact on performance.
|
|
|
|
*
|
|
|
|
* If the firmware is compiled with static addresses, then @da should specify
|
|
|
|
* the expected device address of this memory region. If @da is set to
|
|
|
|
* FW_RSC_ADDR_ANY, then the host will dynamically allocate it, and then
|
|
|
|
* overwrite @da with the dynamically allocated address.
|
|
|
|
*
|
|
|
|
* We will always use @da to negotiate the device addresses, even if it
|
|
|
|
* isn't using an iommu. In that case, though, it will obviously contain
|
|
|
|
* physical addresses.
|
|
|
|
*
|
|
|
|
* Some remote processors needs to know the allocated physical address
|
|
|
|
* even if they do use an iommu. This is needed, e.g., if they control
|
|
|
|
* hardware accelerators which access the physical memory directly (this
|
|
|
|
* is the case with OMAP4 for instance). In that case, the host will
|
|
|
|
* overwrite @pa with the dynamically allocated physical address.
|
|
|
|
* Generally we don't want to expose physical addresses if we don't have to
|
|
|
|
* (remote processors are generally _not_ trusted), so we might want to
|
|
|
|
* change this to happen _only_ when explicitly required by the hardware.
|
|
|
|
*
|
|
|
|
* @flags is used to provide IOMMU protection flags, and @name should
|
|
|
|
* (optionally) contain a human readable name of this carveout region
|
|
|
|
* (mainly for debugging purposes).
|
|
|
|
*/
|
|
|
|
struct fw_rsc_carveout {
|
|
|
|
u32 da;
|
|
|
|
u32 pa;
|
|
|
|
u32 len;
|
|
|
|
u32 flags;
|
|
|
|
u32 reserved;
|
|
|
|
u8 name[32];
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct fw_rsc_devmem - iommu mapping request
|
|
|
|
* @da: device address
|
|
|
|
* @pa: physical address
|
|
|
|
* @len: length (in bytes)
|
|
|
|
* @flags: iommu protection flags
|
|
|
|
* @reserved: reserved (must be zero)
|
|
|
|
* @name: human-readable name of the requested region to be mapped
|
|
|
|
*
|
|
|
|
* This resource entry requests the host to iommu map a physically contiguous
|
|
|
|
* memory region. This is needed in case the remote processor requires
|
|
|
|
* access to certain memory-based peripherals; _never_ use it to access
|
|
|
|
* regular memory.
|
|
|
|
*
|
|
|
|
* This is obviously only needed if the remote processor is accessing memory
|
|
|
|
* via an iommu.
|
|
|
|
*
|
|
|
|
* @da should specify the required device address, @pa should specify
|
|
|
|
* the physical address we want to map, @len should specify the size of
|
|
|
|
* the mapping and @flags is the IOMMU protection flags. As always, @name may
|
|
|
|
* (optionally) contain a human readable name of this mapping (mainly for
|
|
|
|
* debugging purposes).
|
|
|
|
*
|
|
|
|
* Note: at this point we just "trust" those devmem entries to contain valid
|
|
|
|
* physical addresses, but this isn't safe and will be changed: eventually we
|
|
|
|
* want remoteproc implementations to provide us ranges of physical addresses
|
|
|
|
* the firmware is allowed to request, and not allow firmwares to request
|
|
|
|
* access to physical addresses that are outside those ranges.
|
|
|
|
*/
|
|
|
|
struct fw_rsc_devmem {
|
|
|
|
u32 da;
|
|
|
|
u32 pa;
|
|
|
|
u32 len;
|
|
|
|
u32 flags;
|
|
|
|
u32 reserved;
|
|
|
|
u8 name[32];
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct fw_rsc_trace - trace buffer declaration
|
|
|
|
* @da: device address
|
|
|
|
* @len: length (in bytes)
|
|
|
|
* @reserved: reserved (must be zero)
|
|
|
|
* @name: human-readable name of the trace buffer
|
|
|
|
*
|
|
|
|
* This resource entry provides the host information about a trace buffer
|
|
|
|
* into which the remote processor will write log messages.
|
|
|
|
*
|
|
|
|
* @da specifies the device address of the buffer, @len specifies
|
|
|
|
* its size, and @name may contain a human readable name of the trace buffer.
|
|
|
|
*
|
|
|
|
* After booting the remote processor, the trace buffers are exposed to the
|
|
|
|
* user via debugfs entries (called trace0, trace1, etc..).
|
|
|
|
*/
|
|
|
|
struct fw_rsc_trace {
|
|
|
|
u32 da;
|
|
|
|
u32 len;
|
|
|
|
u32 reserved;
|
|
|
|
u8 name[32];
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct fw_rsc_vdev_vring - vring descriptor entry
|
|
|
|
* @da: device address
|
|
|
|
* @align: the alignment between the consumer and producer parts of the vring
|
|
|
|
* @num: num of buffers supported by this vring (must be power of two)
|
|
|
|
* @notifyid is a unique rproc-wide notify index for this vring. This notify
|
|
|
|
* index is used when kicking a remote processor, to let it know that this
|
|
|
|
* vring is triggered.
|
2016-09-06 14:39:43 +07:00
|
|
|
* @pa: physical address
|
2012-02-02 02:56:16 +07:00
|
|
|
*
|
|
|
|
* This descriptor is not a resource entry by itself; it is part of the
|
|
|
|
* vdev resource type (see below).
|
|
|
|
*
|
|
|
|
* Note that @da should either contain the device address where
|
|
|
|
* the remote processor is expecting the vring, or indicate that
|
|
|
|
* dynamically allocation of the vring's device address is supported.
|
|
|
|
*/
|
|
|
|
struct fw_rsc_vdev_vring {
|
|
|
|
u32 da;
|
|
|
|
u32 align;
|
|
|
|
u32 num;
|
|
|
|
u32 notifyid;
|
2016-09-06 14:39:43 +07:00
|
|
|
u32 pa;
|
2012-02-02 02:56:16 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct fw_rsc_vdev - virtio device header
|
|
|
|
* @id: virtio device id (as in virtio_ids.h)
|
|
|
|
* @notifyid is a unique rproc-wide notify index for this vdev. This notify
|
|
|
|
* index is used when kicking a remote processor, to let it know that the
|
|
|
|
* status/features of this vdev have changes.
|
|
|
|
* @dfeatures specifies the virtio device features supported by the firmware
|
|
|
|
* @gfeatures is a place holder used by the host to write back the
|
|
|
|
* negotiated features that are supported by both sides.
|
|
|
|
* @config_len is the size of the virtio config space of this vdev. The config
|
|
|
|
* space lies in the resource table immediate after this vdev header.
|
|
|
|
* @status is a place holder where the host will indicate its virtio progress.
|
|
|
|
* @num_of_vrings indicates how many vrings are described in this vdev header
|
|
|
|
* @reserved: reserved (must be zero)
|
|
|
|
* @vring is an array of @num_of_vrings entries of 'struct fw_rsc_vdev_vring'.
|
|
|
|
*
|
|
|
|
* This resource is a virtio device header: it provides information about
|
|
|
|
* the vdev, and is then used by the host and its peer remote processors
|
|
|
|
* to negotiate and share certain virtio properties.
|
|
|
|
*
|
|
|
|
* By providing this resource entry, the firmware essentially asks remoteproc
|
|
|
|
* to statically allocate a vdev upon registration of the rproc (dynamic vdev
|
|
|
|
* allocation is not yet supported).
|
|
|
|
*
|
|
|
|
* Note: unlike virtualization systems, the term 'host' here means
|
|
|
|
* the Linux side which is running remoteproc to control the remote
|
|
|
|
* processors. We use the name 'gfeatures' to comply with virtio's terms,
|
|
|
|
* though there isn't really any virtualized guest OS here: it's the host
|
|
|
|
* which is responsible for negotiating the final features.
|
|
|
|
* Yeah, it's a bit confusing.
|
|
|
|
*
|
|
|
|
* Note: immediately following this structure is the virtio config space for
|
|
|
|
* this vdev (which is specific to the vdev; for more info, read the virtio
|
|
|
|
* spec). the size of the config space is specified by @config_len.
|
|
|
|
*/
|
|
|
|
struct fw_rsc_vdev {
|
|
|
|
u32 id;
|
|
|
|
u32 notifyid;
|
|
|
|
u32 dfeatures;
|
|
|
|
u32 gfeatures;
|
|
|
|
u32 config_len;
|
|
|
|
u8 status;
|
|
|
|
u8 num_of_vrings;
|
|
|
|
u8 reserved[2];
|
2020-05-08 02:19:43 +07:00
|
|
|
struct fw_rsc_vdev_vring vring[];
|
2012-02-02 02:56:16 +07:00
|
|
|
} __packed;
|
|
|
|
|
2018-07-27 20:14:38 +07:00
|
|
|
struct rproc;
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
/**
|
|
|
|
* struct rproc_mem_entry - memory entry descriptor
|
|
|
|
* @va: virtual address
|
|
|
|
* @dma: dma address
|
|
|
|
* @len: length, in bytes
|
|
|
|
* @da: device address
|
2018-07-27 20:14:38 +07:00
|
|
|
* @release: release associated memory
|
2011-10-20 21:52:46 +07:00
|
|
|
* @priv: associated data
|
2018-07-27 20:14:39 +07:00
|
|
|
* @name: associated memory region name (optional)
|
2011-10-20 21:52:46 +07:00
|
|
|
* @node: list node
|
2018-07-27 20:14:43 +07:00
|
|
|
* @rsc_offset: offset in resource table
|
|
|
|
* @flags: iommu protection flags
|
2018-07-27 20:14:44 +07:00
|
|
|
* @of_resm_idx: reserved memory phandle index
|
2018-07-27 20:14:43 +07:00
|
|
|
* @alloc: specific memory allocator function
|
2011-10-20 21:52:46 +07:00
|
|
|
*/
|
|
|
|
struct rproc_mem_entry {
|
|
|
|
void *va;
|
|
|
|
dma_addr_t dma;
|
2020-03-02 16:38:56 +07:00
|
|
|
size_t len;
|
2012-02-02 02:56:16 +07:00
|
|
|
u32 da;
|
2011-10-20 21:52:46 +07:00
|
|
|
void *priv;
|
2018-07-27 20:14:39 +07:00
|
|
|
char name[32];
|
2011-10-20 21:52:46 +07:00
|
|
|
struct list_head node;
|
2018-07-27 20:14:43 +07:00
|
|
|
u32 rsc_offset;
|
|
|
|
u32 flags;
|
2018-07-27 20:14:44 +07:00
|
|
|
u32 of_resm_idx;
|
2018-07-27 20:14:43 +07:00
|
|
|
int (*alloc)(struct rproc *rproc, struct rproc_mem_entry *mem);
|
2018-07-27 20:14:38 +07:00
|
|
|
int (*release)(struct rproc *rproc, struct rproc_mem_entry *mem);
|
2011-10-20 21:52:46 +07:00
|
|
|
};
|
|
|
|
|
2018-01-06 06:58:01 +07:00
|
|
|
struct firmware;
|
2011-10-20 21:52:46 +07:00
|
|
|
|
2019-06-17 19:57:30 +07:00
|
|
|
/**
|
|
|
|
* enum rsc_handling_status - return status of rproc_ops handle_rsc hook
|
|
|
|
* @RSC_HANDLED: resource was handled
|
|
|
|
* @RSC_IGNORED: resource was ignored
|
|
|
|
*/
|
|
|
|
enum rsc_handling_status {
|
|
|
|
RSC_HANDLED = 0,
|
|
|
|
RSC_IGNORED = 1,
|
|
|
|
};
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
/**
|
|
|
|
* struct rproc_ops - platform-specific device handlers
|
2020-04-17 07:20:35 +07:00
|
|
|
* @prepare: prepare device for code loading
|
|
|
|
* @unprepare: unprepare device after stop
|
2011-10-20 21:52:46 +07:00
|
|
|
* @start: power on the device and boot it
|
|
|
|
* @stop: power off the device
|
|
|
|
* @kick: kick a virtqueue (virtqueue id given as a parameter)
|
2015-05-23 03:45:28 +07:00
|
|
|
* @da_to_va: optional platform hook to perform address translations
|
2018-11-07 17:18:34 +07:00
|
|
|
* @parse_fw: parse firmware to extract information (e.g. resource table)
|
2019-06-17 19:57:30 +07:00
|
|
|
* @handle_rsc: optional platform hook to handle vendor resources. Should return
|
|
|
|
* RSC_HANDLED if resource was handled, RSC_IGNORED if not handled and a
|
|
|
|
* negative value on error
|
|
|
|
* @load_rsc_table: load resource table from firmware image
|
2018-01-06 06:58:01 +07:00
|
|
|
* @find_loaded_rsc_table: find the loaded resouce table
|
2018-11-07 17:18:34 +07:00
|
|
|
* @load: load firmware to memory, where the remote processor
|
2018-01-06 06:58:01 +07:00
|
|
|
* expects to find it
|
|
|
|
* @sanity_check: sanity check the fw image
|
|
|
|
* @get_boot_addr: get boot address to entry point specified in firmware
|
2020-03-24 12:29:02 +07:00
|
|
|
* @panic: optional callback to react to system panic, core will delay
|
|
|
|
* panic at least the returned number of milliseconds
|
2011-10-20 21:52:46 +07:00
|
|
|
*/
|
|
|
|
struct rproc_ops {
|
2020-04-17 07:20:35 +07:00
|
|
|
int (*prepare)(struct rproc *rproc);
|
|
|
|
int (*unprepare)(struct rproc *rproc);
|
2011-10-20 21:52:46 +07:00
|
|
|
int (*start)(struct rproc *rproc);
|
|
|
|
int (*stop)(struct rproc *rproc);
|
|
|
|
void (*kick)(struct rproc *rproc, int vqid);
|
2020-03-02 16:38:55 +07:00
|
|
|
void * (*da_to_va)(struct rproc *rproc, u64 da, size_t len);
|
2018-01-06 07:04:18 +07:00
|
|
|
int (*parse_fw)(struct rproc *rproc, const struct firmware *fw);
|
2019-06-17 19:57:30 +07:00
|
|
|
int (*handle_rsc)(struct rproc *rproc, u32 rsc_type, void *rsc,
|
|
|
|
int offset, int avail);
|
2018-01-06 06:58:01 +07:00
|
|
|
struct resource_table *(*find_loaded_rsc_table)(
|
|
|
|
struct rproc *rproc, const struct firmware *fw);
|
|
|
|
int (*load)(struct rproc *rproc, const struct firmware *fw);
|
|
|
|
int (*sanity_check)(struct rproc *rproc, const struct firmware *fw);
|
2020-03-02 16:38:57 +07:00
|
|
|
u64 (*get_boot_addr)(struct rproc *rproc, const struct firmware *fw);
|
2020-03-24 12:29:02 +07:00
|
|
|
unsigned long (*panic)(struct rproc *rproc);
|
2011-10-20 21:52:46 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* enum rproc_state - remote processor states
|
|
|
|
* @RPROC_OFFLINE: device is powered off
|
|
|
|
* @RPROC_SUSPENDED: device is suspended; needs to be woken up to receive
|
|
|
|
* a message.
|
|
|
|
* @RPROC_RUNNING: device is up and running
|
|
|
|
* @RPROC_CRASHED: device has crashed; need to start recovery
|
2017-01-24 08:53:18 +07:00
|
|
|
* @RPROC_DELETED: device is deleted
|
2011-10-20 21:52:46 +07:00
|
|
|
* @RPROC_LAST: just keep this one at the end
|
|
|
|
*
|
|
|
|
* Please note that the values of these states are used as indices
|
|
|
|
* to rproc_state_string, a state-to-name lookup table,
|
|
|
|
* so please keep the two synchronized. @RPROC_LAST is used to check
|
|
|
|
* the validity of an index before the lookup table is accessed, so
|
|
|
|
* please update it as needed too.
|
|
|
|
*/
|
|
|
|
enum rproc_state {
|
|
|
|
RPROC_OFFLINE = 0,
|
|
|
|
RPROC_SUSPENDED = 1,
|
|
|
|
RPROC_RUNNING = 2,
|
|
|
|
RPROC_CRASHED = 3,
|
2017-01-24 08:53:18 +07:00
|
|
|
RPROC_DELETED = 4,
|
|
|
|
RPROC_LAST = 5,
|
2011-10-20 21:52:46 +07:00
|
|
|
};
|
|
|
|
|
2012-08-31 01:26:12 +07:00
|
|
|
/**
|
|
|
|
* enum rproc_crash_type - remote processor crash types
|
|
|
|
* @RPROC_MMUFAULT: iommu fault
|
2016-03-29 10:36:59 +07:00
|
|
|
* @RPROC_WATCHDOG: watchdog bite
|
|
|
|
* @RPROC_FATAL_ERROR fatal error
|
2012-08-31 01:26:12 +07:00
|
|
|
*
|
|
|
|
* Each element of the enum is used as an array index. So that, the value of
|
|
|
|
* the elements should be always something sane.
|
|
|
|
*
|
|
|
|
* Feel free to add more types when needed.
|
|
|
|
*/
|
|
|
|
enum rproc_crash_type {
|
|
|
|
RPROC_MMUFAULT,
|
2016-03-29 10:36:59 +07:00
|
|
|
RPROC_WATCHDOG,
|
|
|
|
RPROC_FATAL_ERROR,
|
2012-08-31 01:26:12 +07:00
|
|
|
};
|
|
|
|
|
2018-01-06 07:04:17 +07:00
|
|
|
/**
|
|
|
|
* struct rproc_dump_segment - segment info from ELF header
|
|
|
|
* @node: list node related to the rproc segment list
|
|
|
|
* @da: device address of the segment
|
|
|
|
* @size: size of the segment
|
2018-10-17 20:55:23 +07:00
|
|
|
* @priv: private data associated with the dump_segment
|
|
|
|
* @dump: custom dump function to fill device memory segment associated
|
|
|
|
* with coredump
|
2018-01-06 07:04:17 +07:00
|
|
|
*/
|
|
|
|
struct rproc_dump_segment {
|
|
|
|
struct list_head node;
|
|
|
|
|
|
|
|
dma_addr_t da;
|
|
|
|
size_t size;
|
|
|
|
|
2018-10-17 20:55:23 +07:00
|
|
|
void *priv;
|
|
|
|
void (*dump)(struct rproc *rproc, struct rproc_dump_segment *segment,
|
|
|
|
void *dest);
|
2018-01-06 07:04:17 +07:00
|
|
|
loff_t offset;
|
|
|
|
};
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
/**
|
|
|
|
* struct rproc - represents a physical remote processor device
|
2015-05-23 03:45:27 +07:00
|
|
|
* @node: list node of this rproc object
|
2011-10-20 21:52:46 +07:00
|
|
|
* @domain: iommu domain
|
|
|
|
* @name: human readable name of the rproc
|
|
|
|
* @firmware: name of firmware file to be loaded
|
|
|
|
* @priv: private data which belongs to the platform-specific rproc module
|
|
|
|
* @ops: platform-specific start/stop rproc handlers
|
remoteproc: maintain a generic child device for each rproc
For each registered rproc, maintain a generic remoteproc device whose
parent is the low level platform-specific device (commonly a pdev, but
it may certainly be any other type of device too).
With this in hand, the resulting device hierarchy might then look like:
omap-rproc.0
|
- remoteproc0 <---- new !
|
- virtio0
|
- virtio1
|
- rpmsg0
|
- rpmsg1
|
- rpmsg2
Where:
- omap-rproc.0 is the low level device that's bound to the
driver which invokes rproc_register()
- remoteproc0 is the result of this patch, and will be added by the
remoteproc framework when rproc_register() is invoked
- virtio0 and virtio1 are vdevs that are registered by remoteproc
when it realizes that they are supported by the firmware
of the physical remote processor represented by omap-rproc.0
- rpmsg0, rpmsg1 and rpmsg2 are rpmsg devices that represent rpmsg
channels, and are registerd by the rpmsg bus when it gets notified
about their existence
Technically, this patch:
- changes 'struct rproc' to contain this generic remoteproc.x device
- creates a new "remoteproc" type, to which this new generic remoteproc.x
device belong to.
- adds a super simple enumeration method for the indices of the
remoteproc.x devices
- updates all dev_* messaging to use the generic remoteproc.x device
instead of the low level platform-specific device
- updates all dma_* allocations to use the parent of remoteproc.x (where
the platform-specific memory pools, most commonly CMA, are to be found)
Adding this generic device has several merits:
- we can now add remoteproc runtime PM support simply by hooking onto the
new "remoteproc" type
- all remoteproc log messages will now carry a common name prefix
instead of having a platform-specific one
- having a device as part of the rproc struct makes it possible to simplify
refcounting (see subsequent patch)
Thanks to Stephen Boyd <sboyd@codeaurora.org> for suggesting and
discussing these ideas in one of the remoteproc review threads and
to Fernando Guzman Lugo <fernando.lugo@ti.com> for trying them out
with the (upcoming) runtime PM support for remoteproc.
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
2012-05-31 02:01:25 +07:00
|
|
|
* @dev: virtual device for refcounting and common remoteproc behavior
|
2011-10-20 21:52:46 +07:00
|
|
|
* @power: refcount of users who need this rproc powered up
|
|
|
|
* @state: state of the device
|
|
|
|
* @lock: lock which protects concurrent manipulations of the rproc
|
|
|
|
* @dbg_dir: debugfs directory of this rproc device
|
|
|
|
* @traces: list of trace buffers
|
|
|
|
* @num_traces: number of trace buffers
|
|
|
|
* @carveouts: list of physically contiguous memory allocations
|
|
|
|
* @mappings: list of iommu mappings we initiated, needed on shutdown
|
|
|
|
* @bootaddr: address of first instruction to boot rproc with (optional)
|
2012-02-14 04:30:39 +07:00
|
|
|
* @rvdevs: list of remote virtio devices
|
2016-10-20 09:40:02 +07:00
|
|
|
* @subdevs: list of subdevices, to following the running state
|
2012-02-14 04:30:39 +07:00
|
|
|
* @notifyids: idr for dynamically assigning rproc-wide unique notify ids
|
remoteproc: maintain a generic child device for each rproc
For each registered rproc, maintain a generic remoteproc device whose
parent is the low level platform-specific device (commonly a pdev, but
it may certainly be any other type of device too).
With this in hand, the resulting device hierarchy might then look like:
omap-rproc.0
|
- remoteproc0 <---- new !
|
- virtio0
|
- virtio1
|
- rpmsg0
|
- rpmsg1
|
- rpmsg2
Where:
- omap-rproc.0 is the low level device that's bound to the
driver which invokes rproc_register()
- remoteproc0 is the result of this patch, and will be added by the
remoteproc framework when rproc_register() is invoked
- virtio0 and virtio1 are vdevs that are registered by remoteproc
when it realizes that they are supported by the firmware
of the physical remote processor represented by omap-rproc.0
- rpmsg0, rpmsg1 and rpmsg2 are rpmsg devices that represent rpmsg
channels, and are registerd by the rpmsg bus when it gets notified
about their existence
Technically, this patch:
- changes 'struct rproc' to contain this generic remoteproc.x device
- creates a new "remoteproc" type, to which this new generic remoteproc.x
device belong to.
- adds a super simple enumeration method for the indices of the
remoteproc.x devices
- updates all dev_* messaging to use the generic remoteproc.x device
instead of the low level platform-specific device
- updates all dma_* allocations to use the parent of remoteproc.x (where
the platform-specific memory pools, most commonly CMA, are to be found)
Adding this generic device has several merits:
- we can now add remoteproc runtime PM support simply by hooking onto the
new "remoteproc" type
- all remoteproc log messages will now carry a common name prefix
instead of having a platform-specific one
- having a device as part of the rproc struct makes it possible to simplify
refcounting (see subsequent patch)
Thanks to Stephen Boyd <sboyd@codeaurora.org> for suggesting and
discussing these ideas in one of the remoteproc review threads and
to Fernando Guzman Lugo <fernando.lugo@ti.com> for trying them out
with the (upcoming) runtime PM support for remoteproc.
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
2012-05-31 02:01:25 +07:00
|
|
|
* @index: index of this rproc device
|
2012-08-31 01:26:12 +07:00
|
|
|
* @crash_handler: workqueue for handling a crash
|
|
|
|
* @crash_cnt: crash counter
|
2012-09-18 16:26:35 +07:00
|
|
|
* @recovery_disabled: flag that state if recovery was disabled
|
2012-09-19 01:32:45 +07:00
|
|
|
* @max_notifyid: largest allocated notify id.
|
2016-12-30 18:21:38 +07:00
|
|
|
* @table_ptr: pointer to the resource table in effect
|
|
|
|
* @cached_table: copy of the resource table
|
2018-01-06 06:57:59 +07:00
|
|
|
* @table_sz: size of @cached_table
|
2015-01-10 04:21:58 +07:00
|
|
|
* @has_iommu: flag to indicate if remote processor is behind an MMU
|
2018-09-15 07:37:23 +07:00
|
|
|
* @auto_boot: flag to indicate if remote processor should be auto-started
|
2018-01-06 07:04:17 +07:00
|
|
|
* @dump_segments: list of segments in the firmware
|
2018-07-27 20:14:47 +07:00
|
|
|
* @nb_vdev: number of vdev currently handled by rproc
|
2011-10-20 21:52:46 +07:00
|
|
|
*/
|
|
|
|
struct rproc {
|
2015-05-23 03:45:27 +07:00
|
|
|
struct list_head node;
|
2011-10-20 21:52:46 +07:00
|
|
|
struct iommu_domain *domain;
|
|
|
|
const char *name;
|
2020-04-21 06:15:58 +07:00
|
|
|
const char *firmware;
|
2011-10-20 21:52:46 +07:00
|
|
|
void *priv;
|
2018-01-06 06:58:00 +07:00
|
|
|
struct rproc_ops *ops;
|
remoteproc: maintain a generic child device for each rproc
For each registered rproc, maintain a generic remoteproc device whose
parent is the low level platform-specific device (commonly a pdev, but
it may certainly be any other type of device too).
With this in hand, the resulting device hierarchy might then look like:
omap-rproc.0
|
- remoteproc0 <---- new !
|
- virtio0
|
- virtio1
|
- rpmsg0
|
- rpmsg1
|
- rpmsg2
Where:
- omap-rproc.0 is the low level device that's bound to the
driver which invokes rproc_register()
- remoteproc0 is the result of this patch, and will be added by the
remoteproc framework when rproc_register() is invoked
- virtio0 and virtio1 are vdevs that are registered by remoteproc
when it realizes that they are supported by the firmware
of the physical remote processor represented by omap-rproc.0
- rpmsg0, rpmsg1 and rpmsg2 are rpmsg devices that represent rpmsg
channels, and are registerd by the rpmsg bus when it gets notified
about their existence
Technically, this patch:
- changes 'struct rproc' to contain this generic remoteproc.x device
- creates a new "remoteproc" type, to which this new generic remoteproc.x
device belong to.
- adds a super simple enumeration method for the indices of the
remoteproc.x devices
- updates all dev_* messaging to use the generic remoteproc.x device
instead of the low level platform-specific device
- updates all dma_* allocations to use the parent of remoteproc.x (where
the platform-specific memory pools, most commonly CMA, are to be found)
Adding this generic device has several merits:
- we can now add remoteproc runtime PM support simply by hooking onto the
new "remoteproc" type
- all remoteproc log messages will now carry a common name prefix
instead of having a platform-specific one
- having a device as part of the rproc struct makes it possible to simplify
refcounting (see subsequent patch)
Thanks to Stephen Boyd <sboyd@codeaurora.org> for suggesting and
discussing these ideas in one of the remoteproc review threads and
to Fernando Guzman Lugo <fernando.lugo@ti.com> for trying them out
with the (upcoming) runtime PM support for remoteproc.
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
2012-05-31 02:01:25 +07:00
|
|
|
struct device dev;
|
2011-10-20 21:52:46 +07:00
|
|
|
atomic_t power;
|
|
|
|
unsigned int state;
|
|
|
|
struct mutex lock;
|
|
|
|
struct dentry *dbg_dir;
|
|
|
|
struct list_head traces;
|
|
|
|
int num_traces;
|
|
|
|
struct list_head carveouts;
|
|
|
|
struct list_head mappings;
|
2020-03-02 16:38:57 +07:00
|
|
|
u64 bootaddr;
|
2012-02-14 04:30:39 +07:00
|
|
|
struct list_head rvdevs;
|
2016-10-20 09:40:02 +07:00
|
|
|
struct list_head subdevs;
|
2012-02-14 04:30:39 +07:00
|
|
|
struct idr notifyids;
|
remoteproc: maintain a generic child device for each rproc
For each registered rproc, maintain a generic remoteproc device whose
parent is the low level platform-specific device (commonly a pdev, but
it may certainly be any other type of device too).
With this in hand, the resulting device hierarchy might then look like:
omap-rproc.0
|
- remoteproc0 <---- new !
|
- virtio0
|
- virtio1
|
- rpmsg0
|
- rpmsg1
|
- rpmsg2
Where:
- omap-rproc.0 is the low level device that's bound to the
driver which invokes rproc_register()
- remoteproc0 is the result of this patch, and will be added by the
remoteproc framework when rproc_register() is invoked
- virtio0 and virtio1 are vdevs that are registered by remoteproc
when it realizes that they are supported by the firmware
of the physical remote processor represented by omap-rproc.0
- rpmsg0, rpmsg1 and rpmsg2 are rpmsg devices that represent rpmsg
channels, and are registerd by the rpmsg bus when it gets notified
about their existence
Technically, this patch:
- changes 'struct rproc' to contain this generic remoteproc.x device
- creates a new "remoteproc" type, to which this new generic remoteproc.x
device belong to.
- adds a super simple enumeration method for the indices of the
remoteproc.x devices
- updates all dev_* messaging to use the generic remoteproc.x device
instead of the low level platform-specific device
- updates all dma_* allocations to use the parent of remoteproc.x (where
the platform-specific memory pools, most commonly CMA, are to be found)
Adding this generic device has several merits:
- we can now add remoteproc runtime PM support simply by hooking onto the
new "remoteproc" type
- all remoteproc log messages will now carry a common name prefix
instead of having a platform-specific one
- having a device as part of the rproc struct makes it possible to simplify
refcounting (see subsequent patch)
Thanks to Stephen Boyd <sboyd@codeaurora.org> for suggesting and
discussing these ideas in one of the remoteproc review threads and
to Fernando Guzman Lugo <fernando.lugo@ti.com> for trying them out
with the (upcoming) runtime PM support for remoteproc.
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
2012-05-31 02:01:25 +07:00
|
|
|
int index;
|
2012-08-31 01:26:12 +07:00
|
|
|
struct work_struct crash_handler;
|
2016-08-13 06:42:19 +07:00
|
|
|
unsigned int crash_cnt;
|
2012-09-18 16:26:35 +07:00
|
|
|
bool recovery_disabled;
|
2012-09-19 01:32:45 +07:00
|
|
|
int max_notifyid;
|
2013-04-07 18:06:07 +07:00
|
|
|
struct resource_table *table_ptr;
|
2016-12-30 18:21:38 +07:00
|
|
|
struct resource_table *cached_table;
|
2018-01-06 06:57:59 +07:00
|
|
|
size_t table_sz;
|
2015-01-10 04:21:58 +07:00
|
|
|
bool has_iommu;
|
2016-08-12 04:52:50 +07:00
|
|
|
bool auto_boot;
|
2018-01-06 07:04:17 +07:00
|
|
|
struct list_head dump_segments;
|
2018-07-27 20:14:47 +07:00
|
|
|
int nb_vdev;
|
2020-03-02 16:39:02 +07:00
|
|
|
u8 elf_class;
|
2020-04-10 17:24:32 +07:00
|
|
|
u16 elf_machine;
|
2012-02-14 04:30:39 +07:00
|
|
|
};
|
|
|
|
|
2016-10-20 09:40:02 +07:00
|
|
|
/**
|
|
|
|
* struct rproc_subdev - subdevice tied to a remoteproc
|
|
|
|
* @node: list node related to the rproc subdevs list
|
2018-06-26 19:11:59 +07:00
|
|
|
* @prepare: prepare function, called before the rproc is started
|
2018-06-26 19:11:55 +07:00
|
|
|
* @start: start function, called after the rproc has been started
|
|
|
|
* @stop: stop function, called before the rproc is stopped; the @crashed
|
|
|
|
* parameter indicates if this originates from a recovery
|
2018-06-26 19:11:59 +07:00
|
|
|
* @unprepare: unprepare function, called after the rproc has been stopped
|
2016-10-20 09:40:02 +07:00
|
|
|
*/
|
|
|
|
struct rproc_subdev {
|
|
|
|
struct list_head node;
|
|
|
|
|
2018-06-26 19:11:59 +07:00
|
|
|
int (*prepare)(struct rproc_subdev *subdev);
|
2018-06-26 19:11:55 +07:00
|
|
|
int (*start)(struct rproc_subdev *subdev);
|
|
|
|
void (*stop)(struct rproc_subdev *subdev, bool crashed);
|
2018-06-26 19:11:59 +07:00
|
|
|
void (*unprepare)(struct rproc_subdev *subdev);
|
2016-10-20 09:40:02 +07:00
|
|
|
};
|
|
|
|
|
2012-02-14 04:30:39 +07:00
|
|
|
/* we currently support only two vrings per rvdev */
|
2013-04-07 18:06:07 +07:00
|
|
|
|
2012-02-14 04:30:39 +07:00
|
|
|
#define RVDEV_NUM_VRINGS 2
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct rproc_vring - remoteproc vring state
|
|
|
|
* @va: virtual address
|
|
|
|
* @len: length, in bytes
|
|
|
|
* @da: device address
|
2012-02-29 19:42:13 +07:00
|
|
|
* @align: vring alignment
|
2012-02-14 04:30:39 +07:00
|
|
|
* @notifyid: rproc-specific unique vring index
|
|
|
|
* @rvdev: remote vdev
|
|
|
|
* @vq: the virtqueue of this vring
|
|
|
|
*/
|
|
|
|
struct rproc_vring {
|
|
|
|
void *va;
|
|
|
|
int len;
|
|
|
|
u32 da;
|
2012-02-29 19:42:13 +07:00
|
|
|
u32 align;
|
2012-02-14 04:30:39 +07:00
|
|
|
int notifyid;
|
2011-10-20 21:52:46 +07:00
|
|
|
struct rproc_vdev *rvdev;
|
2012-02-14 04:30:39 +07:00
|
|
|
struct virtqueue *vq;
|
2011-10-20 21:52:46 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct rproc_vdev - remoteproc state for a supported virtio device
|
2016-10-20 09:40:06 +07:00
|
|
|
* @refcount: reference counter for the vdev and vring allocations
|
2016-10-20 09:40:09 +07:00
|
|
|
* @subdev: handle for registering the vdev as a rproc subdevice
|
|
|
|
* @id: virtio device id (as in virtio_ids.h)
|
2012-02-14 04:30:39 +07:00
|
|
|
* @node: list node
|
2011-10-20 21:52:46 +07:00
|
|
|
* @rproc: the rproc handle
|
|
|
|
* @vdev: the virio device
|
|
|
|
* @vring: the vrings for this vdev
|
2013-04-07 18:06:07 +07:00
|
|
|
* @rsc_offset: offset of the vdev's resource entry
|
2018-07-27 20:14:47 +07:00
|
|
|
* @index: vdev position versus other vdev declared in resource table
|
2011-10-20 21:52:46 +07:00
|
|
|
*/
|
|
|
|
struct rproc_vdev {
|
2016-10-20 09:40:06 +07:00
|
|
|
struct kref refcount;
|
|
|
|
|
2016-10-20 09:40:09 +07:00
|
|
|
struct rproc_subdev subdev;
|
2019-01-10 20:50:49 +07:00
|
|
|
struct device dev;
|
2016-10-20 09:40:09 +07:00
|
|
|
|
|
|
|
unsigned int id;
|
2012-02-14 04:30:39 +07:00
|
|
|
struct list_head node;
|
2011-10-20 21:52:46 +07:00
|
|
|
struct rproc *rproc;
|
2012-02-14 04:30:39 +07:00
|
|
|
struct rproc_vring vring[RVDEV_NUM_VRINGS];
|
2013-04-07 18:06:07 +07:00
|
|
|
u32 rsc_offset;
|
2018-07-27 20:14:47 +07:00
|
|
|
u32 index;
|
2011-10-20 21:52:46 +07:00
|
|
|
};
|
|
|
|
|
2015-05-23 03:45:27 +07:00
|
|
|
struct rproc *rproc_get_by_phandle(phandle phandle);
|
2017-08-28 12:34:53 +07:00
|
|
|
struct rproc *rproc_get_by_child(struct device *dev);
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
struct rproc *rproc_alloc(struct device *dev, const char *name,
|
2016-08-13 06:42:20 +07:00
|
|
|
const struct rproc_ops *ops,
|
|
|
|
const char *firmware, int len);
|
2012-07-04 20:25:06 +07:00
|
|
|
void rproc_put(struct rproc *rproc);
|
|
|
|
int rproc_add(struct rproc *rproc);
|
|
|
|
int rproc_del(struct rproc *rproc);
|
2016-10-03 07:46:38 +07:00
|
|
|
void rproc_free(struct rproc *rproc);
|
2011-10-20 21:52:46 +07:00
|
|
|
|
2020-04-18 00:00:37 +07:00
|
|
|
struct rproc *devm_rproc_alloc(struct device *dev, const char *name,
|
|
|
|
const struct rproc_ops *ops,
|
|
|
|
const char *firmware, int len);
|
|
|
|
int devm_rproc_add(struct device *dev, struct rproc *rproc);
|
|
|
|
|
2018-07-27 20:14:41 +07:00
|
|
|
void rproc_add_carveout(struct rproc *rproc, struct rproc_mem_entry *mem);
|
|
|
|
|
2018-07-27 20:14:40 +07:00
|
|
|
struct rproc_mem_entry *
|
|
|
|
rproc_mem_entry_init(struct device *dev,
|
2020-03-02 16:38:56 +07:00
|
|
|
void *va, dma_addr_t dma, size_t len, u32 da,
|
2018-07-27 20:14:43 +07:00
|
|
|
int (*alloc)(struct rproc *, struct rproc_mem_entry *),
|
2018-07-27 20:14:40 +07:00
|
|
|
int (*release)(struct rproc *, struct rproc_mem_entry *),
|
|
|
|
const char *name, ...);
|
|
|
|
|
2018-07-27 20:14:44 +07:00
|
|
|
struct rproc_mem_entry *
|
2020-03-02 16:38:56 +07:00
|
|
|
rproc_of_resm_mem_entry_init(struct device *dev, u32 of_resm_idx, size_t len,
|
2018-07-27 20:14:44 +07:00
|
|
|
u32 da, const char *name, ...);
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
int rproc_boot(struct rproc *rproc);
|
|
|
|
void rproc_shutdown(struct rproc *rproc);
|
2012-08-31 01:26:12 +07:00
|
|
|
void rproc_report_crash(struct rproc *rproc, enum rproc_crash_type type);
|
2018-01-06 07:04:17 +07:00
|
|
|
int rproc_coredump_add_segment(struct rproc *rproc, dma_addr_t da, size_t size);
|
2018-10-17 20:55:24 +07:00
|
|
|
int rproc_coredump_add_custom_segment(struct rproc *rproc,
|
|
|
|
dma_addr_t da, size_t size,
|
|
|
|
void (*dumpfn)(struct rproc *rproc,
|
|
|
|
struct rproc_dump_segment *segment,
|
|
|
|
void *dest),
|
|
|
|
void *priv);
|
2020-04-10 17:24:32 +07:00
|
|
|
int rproc_coredump_set_elf_info(struct rproc *rproc, u8 class, u16 machine);
|
2011-10-20 21:52:46 +07:00
|
|
|
|
2012-02-14 04:30:39 +07:00
|
|
|
static inline struct rproc_vdev *vdev_to_rvdev(struct virtio_device *vdev)
|
|
|
|
{
|
2019-01-21 20:55:15 +07:00
|
|
|
return container_of(vdev->dev.parent, struct rproc_vdev, dev);
|
2012-02-14 04:30:39 +07:00
|
|
|
}
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
static inline struct rproc *vdev_to_rproc(struct virtio_device *vdev)
|
|
|
|
{
|
2012-02-14 04:30:39 +07:00
|
|
|
struct rproc_vdev *rvdev = vdev_to_rvdev(vdev);
|
2011-10-20 21:52:46 +07:00
|
|
|
|
|
|
|
return rvdev->rproc;
|
|
|
|
}
|
|
|
|
|
2018-06-26 19:11:57 +07:00
|
|
|
void rproc_add_subdev(struct rproc *rproc, struct rproc_subdev *subdev);
|
2016-10-20 09:40:02 +07:00
|
|
|
|
|
|
|
void rproc_remove_subdev(struct rproc *rproc, struct rproc_subdev *subdev);
|
|
|
|
|
2011-10-20 21:52:46 +07:00
|
|
|
#endif /* REMOTEPROC_H */
|