| /linux/Documentation/hwmon/ |
| H A D | sch5636.rst | 20 their own custom hwmon solution based upon the SCH5636. 23 hwmon solution. The sch5636 driver runs a sanity check on loading to ensure 25 hwmon solution. 32 The Fujitsu Theseus hwmon solution also contains an integrated watchdog.
|
| H A D | ftsteutates.rst | 19 monitoring and thermal management solution. It is builds on the basic
|
| /linux/arch/arm64/boot/dts/marvell/ |
| H A D | ac5x-rd-carrier.dtsi | 17 * the AC5X RD becomes part of the carrier solution. 18 * This is a development/reference solution, not a full commercial solution,
|
| H A D | ac5x-rd-carrier-cn9131.dts | 17 * the AC5X RD becomes part of the carrier solution.
|
| /linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-01 | 37 # obvious that an easy solution to this problem should just be the removal 41 # implications of this recursive issue where the solution is perhaps not so 43 # CORE also consist of a solution to this recursive problem.
|
| /linux/net/smc/ |
| H A D | Kconfig | 6 SMC-R provides a "sockets over RDMA" solution making use of 9 The Linux implementation of the SMC-R solution is designed as
|
| /linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 20 with the proposed solution, and that can lead to difficulties. 24 by excessive latency in the system. The solution they arrived at was a 38 The audio community, however, could not see past the particular solution 53 the right solution to the problem than they were with a specific module. 54 The moral of the story is to focus on the problem - not a specific solution 64 solution address? 87 - There may be elements of the proposed solution which will not be 92 problem; they may have ideas for a better solution, and may be willing 93 to help in the creation of that solution.
|
| /linux/drivers/iio/addac/ |
| H A D | Kconfig | 17 single-channel software configurable input/output solution. 31 quad-channel software configurable input/output solution.
|
| /linux/Documentation/filesystems/ |
| H A D | locks.rst | 45 The solution I have chosen, after much experimentation and discussion, 50 race and deadlock conditions that the current solution was the only
|
| /linux/Documentation/sound/hd-audio/ |
| H A D | dp-mst.rst | 14 The new solution is to create a few PCMs and to dynamically bind pcm to 16 the new solution.
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-diolan-u2c.rst | 18 The Diolan U2C-12 I2C-USB Adapter provides a low cost solution to connect
|
| /linux/Documentation/driver-api/usb/ |
| H A D | persist.rst | 69 What is the solution? 117 Is this the best solution? 122 centralized Logical Volume Manager. Such a solution would allow you 130 solution is much quicker and easier -- and it exists now, a giant
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | Yama.rst | 30 For a solution, some applications use ``prctl(PR_SET_DUMPABLE, ...)`` to 32 do not. A more general solution is to only allow ptrace directly from a
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | error_handling.rst | 39 solution. Alternatively some implementations might directly issue a bus 58 hard-reset might be the best solution.
|
| /linux/drivers/platform/mellanox/ |
| H A D | Kconfig | 37 providing a high performance switching solution for Enterprise Data 71 providing a high performance switching solution for Enterprise Data
|
| /linux/drivers/acpi/dptf/ |
| H A D | Kconfig | 8 level hardware/software solution for power and thermal management.
|
| /linux/Documentation/misc-devices/ |
| H A D | dw-xdata-pcie.rst | 8 Synopsys DesignWare PCIe prototype solution
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | direct-fs-lookup.rst | 29 is currently the only viable solution as only userspace can know for sure
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 246 The solution is not to allow opening device files and ignore 257 The solution to this problem will be presented in point 2) of C). 287 The solution to this as well as B) is not to allow processes 397 The solution for this is to allow the filesystem to be aborted. 430 The solution is basically the same as above.
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | 88pm860x.txt | 13 - marvell,88pm860x-slave-addr: 88pm860x are two chips solution. <reg> stores the I2C address
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | armada-xp-crs328-4c-20s-4s.dtsi | 17 * solution) or the below Device Tree should be adjusted.
|
| H A D | armada-xp-crs305-1g-4s.dtsi | 17 * solution) or the below Device Tree should be adjusted.
|
| H A D | armada-xp-db-xc3-24g4xg.dts | 16 * solution) or the below Device Tree should be adjusted.
|
| H A D | armada-xp-crs326-24g-2s.dtsi | 17 * solution) or the below Device Tree should be adjusted.
|
| /linux/Documentation/security/ |
| H A D | IMA-templates.rst | 23 The proposed solution solves this problem by separating the template 24 management from the remaining IMA code. The core of this solution is the
|