/linux/drivers/pinctrl/intel/ |
H A D | Kconfig | 11 platforms. Supports 3 banks with 102, 28 and 44 gpios. 18 tristate "Intel Cherryview/Braswell pinctrl and GPIO driver" 22 allows configuring of SoC pins and using them as GPIOs. 25 tristate "Intel Lynxpoint pinctrl and GPIO driver" 29 provides an interface that allows configuring of PCH pins and 41 tristate "Intel pinctrl and GPIO platform driver" 46 of Intel PCH pins and using them as GPIOs. Currently the following 52 tristate "Intel Alder Lake pinctrl and GPIO driver" 56 of Intel Alder Lake PCH pins and using them as GPIOs. 59 tristate "Intel Broxton pinctrl and GPIO driver" [all …]
|
/linux/Documentation/filesystems/bcachefs/ |
H A D | CodingStyle.rst | 6 Good development is like gardening, and codebases are our gardens. Tend to them 8 A little weeding here and there goes a long way; don't wait until things have 12 good. But appreciate beauty when you see it - and let people know. 16 A little organizing here and there goes a long way. 20 Good code is readable code, where the structure is simple and leaves nowhere 25 happen (and will have unpredictable or undefined behaviour if it does), or 26 you're not sure if it can happen and not sure how to handle it yet - make it a 30 assertions need to be handled and turned into checks with error paths, and 40 Good assertions drastically and dramatically reduce the amount of testing 46 Good invariants and assertions will hold everywhere in your codebase. This [all …]
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | hist-v4l2.rst | 12 and began to work on documentation, example drivers and applications. 15 another four years and two stable kernel releases until the new API was 28 meaningless ``O_TRUNC`` :c:func:`open()` flag, and the 29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set 32 identifiers are now ordinals instead of flags, and the 33 ``video_std_construct()`` helper function takes id and 40 struct ``video_standard`` and the color subcarrier fields were 53 and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio 55 :ref:`VIDIOC_G_CTRL <VIDIOC_G_CTRL>` and 59 module. The ``YUV422`` and ``YUV411`` planar image formats were added. [all …]
|
H A D | v4l2.rst | 34 Revision and Copyright 45 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter. 49 - Original author of the V4L2 API and documentation. 58 - Original author of the V4L2 API and documentation. 71 - Designed and documented the multi-planar API. 79 - Introduce HSV formats and other minor changes. 83 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls. 91 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl… 96 part can be used and distributed without restrictions. 110 ctrl_class and which. Which is used to select the current value of the [all …]
|
/linux/Documentation/scsi/ |
H A D | ChangeLog.lpfc | 12 for fabric and nport logins out of lpfc_cmpl_els_flogi. 18 PRLI...) are errored back and scan() terminates. 28 find command in both TX and TX completion queues. Return ERROR 62 - kill struct lpfc_scsi_dma_buf and embedded the two members 67 ever used by the driver, just reported to userspace (and that in 72 32bit and 64bit defines on some archs. 82 * Revise TRANSPORT_PATCHES_V2 so that lpfc_target is removed and 84 * Changed RW attributes of scan_down, max_luns and fcp_bind_method 88 list and marked for ADISC. 102 * Use DMA_64BIT_MASK and DMA_32BIT_MASK defines instead of [all …]
|
/linux/LICENSES/dual/ |
H A D | CC-BY-4.0 | 19 Creative Commons Corporation ("Creative Commons") is not a law firm and 22 other relationship. Creative Commons makes its licenses and related 25 terms and conditions, or any related information. Creative Commons 31 Creative Commons public licenses provide a standard set of terms and 32 conditions that creators and other rights holders may use to share 33 original works of authorship and other material subject to copyright 34 and certain other rights specified in the public license below. The 36 exhaustive, and do not form part of our licenses. 41 copyright and certain other rights. Our licenses are 42 irrevocable. Licensors should read and understand the terms [all …]
|
H A D | Apache-2.0 | 20 TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 24 "License" shall mean the terms and conditions for use, reproduction, and 30 "Legal Entity" shall mean the union of the acting entity and all other 43 and configuration files. 47 object code, generated documentation, and conversions to other media types. 55 that is based on (or derived from) the Work and for which the editorial 59 merely link (or bind by name) to the interfaces of, the Work and Derivative 63 version of the Work and any modifications or additions to that Work or 70 mailing lists, source code control systems, and issue tracking systems that 72 and improving the Work, but excluding communication that is conspicuously [all …]
|
/linux/Documentation/timers/ |
H A D | hrtimers.rst | 9 back and forth trying to integrate high-resolution and high-precision 10 features into the existing timer framework, and after testing various 14 to solve this'), and spent a considerable effort trying to integrate 18 - the forced handling of low-resolution and high-resolution timers in 19 the same way leads to a lot of compromises, macro magic and #ifdef 20 mess. The timers.c code is very "tightly coded" around jiffies and 21 32-bitness assumptions, and has been honed and micro-optimized for a 23 for many years - and thus even small extensions to it easily break 25 code is very good and tight code, there's zero problems with it in its 45 error conditions in various I/O paths, such as networking and block [all …]
|
/linux/Documentation/userspace-api/ |
H A D | dma-buf-alloc-exchange.rst | 9 support for sharing pixel-buffer allocations between processes, devices, and 11 classes; this document details how applications and kernel subsystems should 14 It is written with reference to the DRM subsystem for GPU and display devices, 15 V4L2 for media devices, and also to Vulkan, EGL and Wayland, for userspace 16 support, however any other subsystems should also follow this design and advice. 26 in one or more memory buffers. Has width and height in pixels, pixel 27 format and modifier (implicit or explicit). 41 A piece of memory for storing (parts of) pixel data. Has stride and size 42 in bytes and at least one handle in some API. May contain one or more 46 A two-dimensional array of some or all of an image's color and alpha [all …]
|
/linux/Documentation/fb/ |
H A D | api.rst | 12 with frame buffer devices. In-kernel APIs between device drivers and the frame 16 behaviours differ in subtle (and not so subtle) ways. This document describes 24 Device and driver capabilities are reported in the fixed screen information 34 expect from the device and driver. 43 2. Types and visuals 50 Formats are described by frame buffer types and visuals. Some visuals require 52 bits_per_pixel, grayscale, red, green, blue and transp fields. 54 Visuals describe how color information is encoded and assembled to create 56 types and visuals are supported. 64 Padding at end of lines may be present and is then reported through the fixed [all …]
|
/linux/LICENSES/deprecated/ |
H A D | GPL-1.0 | 18 Everyone is permitted to copy and distribute verbatim copies 25 License is intended to guarantee your freedom to share and change free 28 software and to any other program whose authors commit to using it. 36 programs; and that you know you can do these things. 46 source code. And you must tell them their rights. 48 We protect your rights with two steps: (1) copyright the software, and 50 distribute and/or modify the software. 52 Also, for each author's protection and ours, we want to make certain 54 software. If the software is modified by someone else and passed on, we 59 The precise terms and conditions for copying, distribution and [all …]
|
/linux/Documentation/driver-api/surface_aggregator/ |
H A D | internal.rst | 49 and Surface Serial Hub (SSH) driver. For the API documentation, refer to: 66 the packet transport logic and handles things like packet validation, packet 67 acknowledgment (ACKing), packet (retransmission) timeouts, and relaying 72 responses of the EC to those requests, and events (sent from EC to host). 74 responses to their corresponding requests, and implements request timeouts. 76 The *controller* layer is building on top of this and essentially decides 77 how request responses and, especially, events are dealt with. It provides an 79 workqueue for event and asynchronous request completion, and also manages 86 native SSAM devices, i.e. devices that are not defined in ACPI and not 87 implemented as platform devices, via |ssam_device| and |ssam_device_driver| [all …]
|
/linux/drivers/pinctrl/qcom/ |
H A D | Kconfig.msm | 8 This is the pinctrl, pinmux, pinconf and gpiolib driver for the 15 This is the pinctrl, pinmux, pinconf and gpiolib driver for the 22 This is the pinctrl, pinmux, pinconf and gpiolib driver for the 29 This is the pinctrl, pinmux, pinconf and gpiolib driver for 38 This is the pinctrl, pinmux, pinconf and gpiolib driver for the 45 This is the pinctrl, pinmux, pinconf and gpiolib driver for the 53 This is the pinctrl, pinmux, pinconf and gpiolib driver for 62 This is the pinctrl, pinmux, pinconf and gpiolib driver for 71 This is the pinctrl, pinmux, pinconf and gpiolib driver for 80 This is the pinctrl, pinmux, pinconf and gpiolib driver for [all …]
|
/linux/tools/perf/pmu-events/arch/x86/westmereep-dp/ |
H A D | memory.json | 11 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = ANY_DRAM AND REMOTE_FWD", 21 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = ANY_LLC_MISS", 31 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = OTHER_LOCAL_DRAM", 41 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = REMOTE_DRAM", 51 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = ANY_DRAM AND REMOTE_FWD", 61 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = ANY_LLC_MISS", 71 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = OTHER_LOCAL_DRAM", 81 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = REMOTE_DRAM", 91 "BriefDescription": "REQUEST = ANY_REQUEST and RESPONSE = ANY_DRAM AND REMOTE_FWD", 101 "BriefDescription": "REQUEST = ANY_REQUEST and RESPONSE = ANY_LLC_MISS", [all …]
|
/linux/Documentation/driver-api/usb/ |
H A D | gadget.rst | 12 within peripherals and other USB devices that embed Linux. It provides 13 an overview of the API structure, and shows how that fits into a system 26 and alternate interface settings. 31 - Sharing data structures and API models with the Linux-USB host side 32 API. This helps the OTG support, and looks forward to more-symmetric 33 frameworks (where the same I/O model is used by both host and device 47 driver is the master (or "client driver") and the gadget driver is the 51 queues of request objects to package I/O buffers, and those requests may 53 USB *Chapter 9* messages, structures, and constants. Also, both APIs 54 bind and unbind drivers to devices. The APIs differ in detail, since the [all …]
|
/linux/LICENSES/preferred/ |
H A D | GPL-2.0 | 25 Everyone is permitted to copy and distribute verbatim copies 31 freedom to share and change it. By contrast, the GNU General Public 32 License is intended to guarantee your freedom to share and change free 35 Foundation's software and to any other program whose authors commit to 42 have the freedom to distribute copies of free software (and charge for 45 in new free programs; and that you know you can do these things. 55 source code. And you must show them these terms so they know their 58 We protect your rights with two steps: (1) copyright the software, and 60 distribute and/or modify the software. 62 Also, for each author's protection and ours, we want to make certain [all …]
|
H A D | LGPL-2.0 | 21 Everyone is permitted to copy and distribute verbatim copies of this 30 share and change it. By contrast, the GNU General Public Licenses are 31 intended to guarantee your freedom to share and change free software--to 35 designated Free Software Foundation software, and to any other libraries 40 to distribute copies of free software (and charge for this service if you 42 can change the software or use pieces of it in new free programs; and that 55 changes to the library and recompiling it. And you must show them these 59 library, and (2) offer you this license which gives you legal permission to 60 copy, distribute and/or modify the library. 64 the library is modified by someone else and passed on, we want its [all …]
|
H A D | LGPL-2.1 | 23 Everyone is permitted to copy and distribute verbatim copies of this 33 share and change it. By contrast, the GNU General Public Licenses are 34 intended to guarantee your freedom to share and change free software--to 39 Foundation and other authors who decide to use it. You can use it too, but 46 the freedom to distribute copies of free software (and charge for this 48 want it; that you can change the software and use pieces of it in new free 49 programs; and that you are informed that you can do these things. 61 changes to the library and recompiling it. And you must show them these 65 library, and (2) we offer you this license, which gives you legal 66 permission to copy, distribute and/or modify the library. [all …]
|
/linux/tools/usb/usbip/ |
H A D | COPYING | 6 Everyone is permitted to copy and distribute verbatim copies 12 freedom to share and change it. By contrast, the GNU General Public 13 License is intended to guarantee your freedom to share and change free 16 Foundation's software and to any other program whose authors commit to 23 have the freedom to distribute copies of free software (and charge for 26 in new free programs; and that you know you can do these things. 36 source code. And you must show them these terms so they know their 39 We protect your rights with two steps: (1) copyright the software, and 41 distribute and/or modify the software. 43 Also, for each author's protection and ours, we want to make certain [all …]
|
/linux/Documentation/arch/x86/ |
H A D | intel_txt.rst | 15 - Measurement and verification of launched environment 17 Intel TXT is part of the vPro(TM) brand and is also available some 19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell 20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45, 21 PM45, and GS45 Express chipsets. 47 uses Intel TXT to perform a measured and verified launch of an OS 55 w/ TXT support since v3.2), and now Linux kernels. 61 While there are many products and technologies that attempt to 64 Measurement Architecture (IMA) and Linux Integrity Module interface 69 starting at system reset and requires measurement of all code [all …]
|
/linux/drivers/hwmon/ |
H A D | Kconfig | 14 sensors and various additional features such as the ability to 16 should say Y here and also to the specific driver(s) for your 36 a problem with I2C support and want to see more of what is going 46 and second revision of the Abit uGuru chip. The voltage and frequency 49 Abit motherboards from before end 2005). For more info and a list 62 and their settings is supported. The third revision of the Abit 64 2005). For more info and a list of which motherboards have which 75 current and power sensors of Ampere's Altra processor family SoC 79 tristate "Analog Devices AD7314 and compatibles" 83 AD7314, ADT7301 and ADT7302 temperature sensors. [all …]
|
/linux/Documentation/RCU/ |
H A D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by 7 and search engines will usually find what you are looking for. 9 The first thing resembling RCU was published in 1980, when Kung and Lehman 16 In 1982, Manber and Ladner [Manber82,Manber84] recommended deferring 22 In 1986, Hennessy, Osisek, and Seigh [Hennessy89] introduced passive 47 write-side contention and parallelize the other write-side overheads by 56 error, which typically slows convergence and thus increases the number of 61 structured data, such as the matrices used in scientific programs, and 88 Their approach requires memory barriers (and thus pipeline stalls), 89 but reduces memory latency, contention, and locking overheads. [all …]
|
/linux/tools/memory-model/Documentation/ |
H A D | explanation.txt | 13 5. ORDERING AND CYCLES 15 7. THE PROGRAM ORDER RELATION: po AND po-loc 17 9. DEPENDENCY RELATIONS: data, addr, and ctrl 18 10. THE READS-FROM RELATION: rf, rfi, and rfe 19 11. CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe 20 12. THE FROM-READS RELATION: fr, fri, and fre 27 19. AND THEN THERE WAS ALPHA 30 22. RCU RELATIONS: rcu-link, rcu-gp, rcu-rscsi, rcu-order, rcu-fence, and rb 33 25. PLAIN ACCESSES AND DATA RACES 34 26. ODDS AND ENDS [all …]
|
/linux/Documentation/usb/ |
H A D | CREDITS | 31 Linux USB driver effort and writing much of the larger uusbd driver. 35 and offering suggestions and sharing implementation experiences. 37 Additional thanks to the following companies and people for donations 38 of hardware, support, time and development (this is from the original 44 - 3Com GmbH for donating a ISDN Pro TA and supporting me 45 in technical questions and with test equipment. I'd never 52 Operating System and supports this project with 74 protocol. They've also donated a F-23 digital joystick and a 79 leading manufacturer for active and passive ISDN Controllers 80 and CAPI 2.0-based software. The active design of the AVM B1 [all …]
|
/linux/include/linux/ |
H A D | zlib.h | 3 Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler 10 including commercial applications, and to alter it and redistribute it 17 2. Altered source versions must be plainly marked as such, and must not be 27 (zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format). 43 * Z_PACKET_FLUSH is added and used by ppp_deflate. Before returning 44 this checks there is no more input data available and the next data 48 the history window and adjusts the accoutning without calling 53 The 'zlib' compression library provides in-memory compression and 56 (deflation) but other algorithms will be added later and will have the same 62 application must provide more input and/or consume the output [all …]
|