Home
last modified time | relevance | path

Searched full:technically (Results 1 – 25 of 236) sorted by relevance

12345678910

/linux-6.14.4/drivers/mfd/
Drk8xx-i2c.c39 * - Technically the ROUND_30s bit makes RTC_CTRL_REG volatile, but in rk808_is_volatile_reg()
66 * Technically the ROUND_30s bit makes RTC_CTRL_REG volatile, but in rk816_is_volatile_reg()
96 * - Technically the ROUND_30s bit makes RTC_CTRL_REG volatile, but in rk817_is_volatile_reg()
/linux-6.14.4/tools/testing/selftests/kvm/include/x86/
Dpmu.h14 * technically AMD's format, as Intel's format only supports 8 bits for the
23 * These are technically Intel's definitions, but except for CMASK (see above),
/linux-6.14.4/arch/arm64/boot/dts/qcom/
Dsdm845-cheza-r1.dts21 * NOTE: Technically pp3500_a is not the exact same signal as
55 * L19 and L28 technically go to 3.3V, but most boards have old AOP firmware
Dsdm845-cheza-r2.dts21 * NOTE: Technically pp3500_a is not the exact same signal as
55 * L19 and L28 technically go to 3.3V, but most boards have old AOP firmware
/linux-6.14.4/kernel/configs/
Dxen.config17 # Technically not required but otherwise produces
/linux-6.14.4/drivers/base/regmap/
Dregmap-sdw-mbq.c109 * Technically the spec does allow a device to set itself to busy for in regmap_sdw_mbq_write()
169 * Technically the spec does allow a device to set itself to busy for in regmap_sdw_mbq_read()
/linux-6.14.4/Documentation/devicetree/bindings/fpga/
Daltr,fpga-passive-serial.yaml15 The passive serial link is not technically SPI, and might require extra
Dxlnx,fpga-slave-serial.yaml15 not technically SPI, and might require extra circuits in order to play nicely
/linux-6.14.4/drivers/ssb/
Db43_pci_bridge.c4 * This technically is a separate PCI driver module, but
/linux-6.14.4/drivers/staging/media/av7110/
DKconfig57 # While technically independent, it doesn't make sense to keep
/linux-6.14.4/drivers/clk/davinci/
Dpll-da830.c27 * NB: Technically, the clocks flagged as SYSCLK_FIXED_DIV are "fixed ratio",
/linux-6.14.4/tools/testing/selftests/power_supply/
Dtest_power_supply_properties.sh86 # Technically the power-supply class does not limit reported values.
/linux-6.14.4/include/linux/lockd/
Dxdr.h51 * NLM cookies. Technically they can be 1K, but Linux only uses 8 bytes.
/linux-6.14.4/arch/hexagon/kernel/
Dvm_switch.S34 * in the new R0's pointer. Technically it should be R2, but they should
/linux-6.14.4/arch/arm/kernel/
Dhibernate.c53 * soft_restart is not technically needed, but is used to get success
/linux-6.14.4/tools/testing/selftests/bpf/
Dgenerate_udp_fragments.py7 While it is technically possible to dynamically generate
/linux-6.14.4/Documentation/devicetree/bindings/iio/adc/
Dadi,ad7780.yaml68 GPIO reading the R̅D̅Y̅ line. Having such a GPIO is technically optional but
Dadi,ad7124.yaml42 GPIO reading the R̅D̅Y̅ line. Having such a GPIO is technically optional but
/linux-6.14.4/arch/arm/mach-imx/
Dcpu-imx5.c122 * Technically it is only required while perf is used, but to
/linux-6.14.4/arch/microblaze/include/asm/
Dhash.h7 * both multiplier and barrel shifter, but omitting them is technically
/linux-6.14.4/tools/testing/selftests/kvm/x86/
Dxcr0_cpuid_test.c36 * disabled coherently. E.g. a CPU can technically enumerate supported for
/linux-6.14.4/arch/arm/mach-omap2/
Dopp2430_data.c27 * This is technically part of the OMAP2xxx clock code.
Dopp2420_data.c23 * This is technically part of the OMAP2xxx clock code.
/linux-6.14.4/tools/testing/selftests/powerpc/dexcr/
Ddexcr.c135 * 1. The LR value (any register technically)
/linux-6.14.4/Documentation/locking/
Drt-mutex.rst75 BTW, there is still technically a "Pending Owner", it's just not called

12345678910