fsnotify: unified filesystem notification backend
[GitHub/mt8127/android_kernel_alcatel_ttab.git] / include / linux / virtio_config.h
CommitLineData
ec3d41c4
RR
1#ifndef _LINUX_VIRTIO_CONFIG_H
2#define _LINUX_VIRTIO_CONFIG_H
674bfc23
RR
3/* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so
4 * anyone can use the definitions to implement compatible drivers/servers. */
5
ec3d41c4
RR
6/* Virtio devices use a standardized configuration space to define their
7 * features and pass configuration information, but each implementation can
8 * store and access that space differently. */
9#include <linux/types.h>
10
a586d4f6 11/* Status byte for guest to report progress, and synchronize features. */
ec3d41c4
RR
12/* We have seen device and processed generic fields (VIRTIO_CONFIG_F_VIRTIO) */
13#define VIRTIO_CONFIG_S_ACKNOWLEDGE 1
14/* We have found a driver for the device. */
15#define VIRTIO_CONFIG_S_DRIVER 2
16/* Driver has used its parts of the config, and is happy */
17#define VIRTIO_CONFIG_S_DRIVER_OK 4
18/* We've given up on this device. */
19#define VIRTIO_CONFIG_S_FAILED 0x80
20
dd7c7bc4
RR
21/* Some virtio feature bits (currently bits 28 through 31) are reserved for the
22 * transport being used (eg. virtio_ring), the rest are per-device feature
23 * bits. */
24#define VIRTIO_TRANSPORT_F_START 28
25#define VIRTIO_TRANSPORT_F_END 32
26
b4f68be6
RR
27/* Do we get callbacks when the ring is completely used, even if we've
28 * suppressed them? */
29#define VIRTIO_F_NOTIFY_ON_EMPTY 24
30
ec3d41c4 31#ifdef __KERNEL__
72e61eb4 32#include <linux/virtio.h>
ec3d41c4
RR
33
34/**
35 * virtio_config_ops - operations for configuring a virtio device
a586d4f6 36 * @get: read the value of a configuration field
ec3d41c4 37 * vdev: the virtio_device
a586d4f6 38 * offset: the offset of the configuration field
ec3d41c4 39 * buf: the buffer to write the field value into.
a586d4f6 40 * len: the length of the buffer
a586d4f6 41 * @set: write the value of a configuration field
ec3d41c4 42 * vdev: the virtio_device
a586d4f6 43 * offset: the offset of the configuration field
ec3d41c4 44 * buf: the buffer to read the field value from.
a586d4f6 45 * len: the length of the buffer
ec3d41c4
RR
46 * @get_status: read the status byte
47 * vdev: the virtio_device
48 * Returns the status byte
49 * @set_status: write the status byte
50 * vdev: the virtio_device
51 * status: the new status byte
6e5aa7ef
RR
52 * @reset: reset the device
53 * vdev: the virtio device
54 * After this, status and feature negotiation must be done again
a586d4f6 55 * @find_vq: find a virtqueue and instantiate it.
ec3d41c4 56 * vdev: the virtio_device
a586d4f6 57 * index: the 0-based virtqueue number in case there's more than one.
ec3d41c4 58 * callback: the virqtueue callback
a586d4f6 59 * Returns the new virtqueue or ERR_PTR() (eg. -ENOENT).
ec3d41c4 60 * @del_vq: free a virtqueue found by find_vq().
c45a6816
RR
61 * @get_features: get the array of feature bits for this device.
62 * vdev: the virtio_device
63 * Returns the first 32 feature bits (all we currently need).
c624896e 64 * @finalize_features: confirm what device features we'll be using.
c45a6816 65 * vdev: the virtio_device
c624896e
RR
66 * This gives the final feature bits for the device: it can change
67 * the dev->feature bits if it wants.
ec3d41c4
RR
68 */
69struct virtio_config_ops
70{
a586d4f6 71 void (*get)(struct virtio_device *vdev, unsigned offset,
ec3d41c4 72 void *buf, unsigned len);
a586d4f6 73 void (*set)(struct virtio_device *vdev, unsigned offset,
ec3d41c4
RR
74 const void *buf, unsigned len);
75 u8 (*get_status)(struct virtio_device *vdev);
76 void (*set_status)(struct virtio_device *vdev, u8 status);
6e5aa7ef 77 void (*reset)(struct virtio_device *vdev);
ec3d41c4 78 struct virtqueue *(*find_vq)(struct virtio_device *vdev,
a586d4f6 79 unsigned index,
18445c4d 80 void (*callback)(struct virtqueue *));
ec3d41c4 81 void (*del_vq)(struct virtqueue *vq);
c45a6816 82 u32 (*get_features)(struct virtio_device *vdev);
c624896e 83 void (*finalize_features)(struct virtio_device *vdev);
ec3d41c4
RR
84};
85
c45a6816
RR
86/* If driver didn't advertise the feature, it will never appear. */
87void virtio_check_driver_offered_feature(const struct virtio_device *vdev,
88 unsigned int fbit);
89
90/**
91 * virtio_has_feature - helper to determine if this device has this feature.
92 * @vdev: the device
93 * @fbit: the feature bit
94 */
95static inline bool virtio_has_feature(const struct virtio_device *vdev,
96 unsigned int fbit)
97{
98 /* Did you forget to fix assumptions on max features? */
99 if (__builtin_constant_p(fbit))
100 BUILD_BUG_ON(fbit >= 32);
101
102 virtio_check_driver_offered_feature(vdev, fbit);
103 return test_bit(fbit, vdev->features);
104}
105
ec3d41c4 106/**
72e61eb4 107 * virtio_config_val - look for a feature and get a virtio config entry.
a586d4f6
RR
108 * @vdev: the virtio device
109 * @fbit: the feature bit
110 * @offset: the type to search for.
ec3d41c4
RR
111 * @val: a pointer to the value to fill in.
112 *
a586d4f6 113 * The return value is -ENOENT if the feature doesn't exist. Otherwise
72e61eb4
RR
114 * the config value is copied into whatever is pointed to by v. */
115#define virtio_config_val(vdev, fbit, offset, v) \
7f31fe05 116 virtio_config_buf((vdev), (fbit), (offset), (v), sizeof(*v))
ec3d41c4 117
72e61eb4
RR
118static inline int virtio_config_buf(struct virtio_device *vdev,
119 unsigned int fbit,
120 unsigned int offset,
121 void *buf, unsigned len)
122{
c45a6816 123 if (!virtio_has_feature(vdev, fbit))
72e61eb4
RR
124 return -ENOENT;
125
126 vdev->config->get(vdev, offset, buf, len);
127 return 0;
128}
ec3d41c4
RR
129#endif /* __KERNEL__ */
130#endif /* _LINUX_VIRTIO_CONFIG_H */