| /linux/drivers/cdrom/ |
| H A D | cdrom.c | 977 static void cdrom_count_tracks(struct cdrom_device_info *cdi, tracktype *tracks) in cdrom_count_tracks() argument
982 tracks->data = 0; in cdrom_count_tracks()
983 tracks->audio = 0; in cdrom_count_tracks()
984 tracks->cdi = 0; in cdrom_count_tracks()
985 tracks->xa = 0; in cdrom_count_tracks()
986 tracks->error = 0; in cdrom_count_tracks()
990 tracks->error = CDS_NO_INFO; in cdrom_count_tracks()
998 tracks->error = CDS_NO_DISC; in cdrom_count_tracks()
1000 tracks->error = CDS_NO_INFO; in cdrom_count_tracks()
1008 tracks->error = CDS_NO_INFO; in cdrom_count_tracks()
[all …]
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | vmscape.rst | 38 Kernel tracks when a CPU has run a potentially malicious guest and issues an
85 Conditional IBPB mitigation is enabled. The kernel tracks when a CPU has
|
| /linux/include/uapi/linux/ |
| H A D | fd.h | 146 unsigned char tracks; /* maximum number of tracks */ member
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 155 ``rcu_node`` and ``rcu_data`` structures, tracks grace periods,
157 events, maintains ``rcu_barrier()`` state, tracks expedited
174 detection and RCU callback queuing. It also tracks its relationship
181 and also tracks statistics.
197 between the ``rcu_node`` and ``rcu_data`` structures, tracks grace
333 The ``->gp_max`` field tracks the duration of the longest grace period
463 The ``->qsmask`` field tracks which of this ``rcu_node`` structure's
468 Similarly, the ``->expmask`` field tracks which of this ``rcu_node``
475 tens of microseconds. The ``->qsmaskinit`` field tracks which of this
522 know that the ``rcu_node`` structure tracks them.
[all …]
|
| /linux/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 12 tracks VFIO files (group or device) in use by the VM and features
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | knfsd-stats.rst | 67 The circumstance this statistic tracks indicates that there was NFS
82 This statistic tracks the circumstance where incoming
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | orphan.rst | 14 Traditionally ext4 tracks orphan inodes in a form of single linked list where
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-modulator.rst | 167 tracks. When the input has three channels the mono track is a
173 channel it is used for all audio tracks. It is not possible to
|
| /linux/Documentation/mm/ |
| H A D | page_frags.rst | 18 and tracks allows multiple calls to make use of a cached page. The
|
| /linux/Documentation/cdrom/ |
| H A D | cdrom-standard.rst | 498 reading audio tracks as data, I believe this is because of protection
499 of copyrights of artists. Moreover, I think that if audio-tracks are
708 set, that it contains tracks of type `data mode 1`. Only if all tests
931 also very common for CDs to have some tracks with data, and some
932 tracks with audio. Because this is an existing interface, rather
936 follows: If the CD in question has audio tracks on it, and it has
937 absolutely no CD-I, XA, or data tracks on it, it will be reported
938 as *CDS_AUDIO*. If it has both audio and data tracks, it will
939 return *CDS_MIXED*. If there are no audio tracks on the disc, and
940 if the CD in question has any CD-I tracks on it, it will be
[all …]
|
| /linux/Documentation/userspace-api/ioctl/ |
| H A D | cdrom.rst | 949 very common for CDs to have some tracks with data, and some
950 tracks with audio. Just because I feel like it, I declare
952 ANY data tracks on it, it will be returned as a data CD.
953 If it has any XA tracks, I will return it as that. Now I
|
| /linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 67 `error_count` tracks the number of errors that occurred and were
|
| H A D | rtc.rst | 6 something that tracks wall clock time and is battery backed so that it
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | fw_upload.rst | 126 * remaining_size - tracks the data transfer portion of an update
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | pids.rst | 34 pids.current tracks all child cgroup hierarchies, so parent/pids.current is a
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | cache-policies.rst | 97 away. In addition it tracks performance of the hotspot queue, which
|
| /linux/Documentation/locking/ |
| H A D | lockstat.rst | 80 It also tracks 4 contention points per class. A contention point is a call site
|
| H A D | lockdep-design.rst | 19 The validator tracks the 'usage state' of lock-classes, and it tracks
41 The validator tracks lock-class usage history and divides the usage into
339 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-dax | 79 (RO) The available_size attribute tracks available dax region
|
| /linux/arch/m68k/include/asm/ |
| H A D | atarihw.h | 383 u_char tracks; member
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | architecture.rst | 34 Each KUnit test case receives a ``struct kunit`` context object that tracks a
|
| /linux/Documentation/arch/x86/ |
| H A D | pat.rst | 112 In addition, step 2 internally tracks the region as UC or WC in memtype
|
| H A D | orc-unwinder.rst | 86 end up having to track all the registers DWARF tracks, at least we will
|
| /linux/Documentation/process/debugging/ |
| H A D | driver_development_debugging_guide.rst | 194 It tracks lock acquisitions and releases, building a dependency graph that is
|
| /linux/Documentation/filesystems/iomap/ |
| H A D | operations.rst | 169 tracks the per-fsblock uptodate and dirty state itself.
174 iomap internally tracks two state bits per fsblock:
187 iomap also tracks the amount of read and write disk IOs that are in
|