| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | berlin,pinctrl.txt | 13 Be aware the Marvell Berlin datasheets use the keyword 'mode' for what
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | davinci_emac.txt | 3 This file provides information, what the device node
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-get-info.rst | 45 Capabilities describe what a frontend can do. Some capabilities are
|
| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-davinci.txt | 3 This file provides information, what the device node for the
|
| /openbmc/openbmc/meta-phosphor/recipes-core/os-release/ |
| H A D | os-release.bbappend | 6 # what that means!
|
| /openbmc/google-misc/subprojects/nemora-postd/ |
| H A D | README.md | 57 what you set via `busctl`.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/linuxptp/linuxptp/ |
| H A D | 0002-linuxptp-Use-CC-in-incdefs.sh.patch | 8 compilers depending on what the user pass during make invocation
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-numpy_1.26.4.bb | 35 # install what is needed for numpy.test()
|
| /openbmc/linux/fs/ext2/ |
| H A D | Kconfig | 32 If you don't know what Access Control Lists are, say N
|
| /openbmc/linux/fs/9p/ |
| H A D | Kconfig | 30 If you don't know what Access Control Lists are, say N
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/backlight/ |
| H A D | common.yaml | 31 on the brightness apart from what the driver says, as it could happen
|
| /openbmc/linux/Documentation/devicetree/bindings/misc/ |
| H A D | ti,j721e-esm.yaml | 15 that allows handling of safety events somewhat similar to what interrupt
|
| /openbmc/openpower-pnor-code-mgmt/ |
| H A D | item_updater_main.cpp | 134 log<level::ERR>(e.what()); in main()
|
| /openbmc/openbmc/poky/meta/recipes-graphics/vulkan/ |
| H A D | vulkan-loader_1.3.283.0.bb | 41 # The tags versions should always be sdk-x.y.z, as this is what
|
| /openbmc/linux/Documentation/process/ |
| H A D | applying-patches.rst | 15 a patch to the kernel or, more specifically, what base kernel a patch for
31 To correctly apply a patch you need to know what base it was generated from
32 and what new version the patch will change the source tree into. These
51 local machine (but is often useful info to see what version an otherwise
95 (what I assume you've done in the examples below), then you simply run
107 what would happen, but doesn't actually make any changes. Finally ``--verbose``
141 read this file to see exactly what change couldn't be applied, so you can
361 development branches and is also what will eventually turn into the next
|
| /openbmc/intel-ipmi-oem/src/ |
| H A D | oemcommands.cpp | 399 phosphor::logging::entry("EXCEPTION=%s", e.what())); in ipmiOEMDisableBMCSystemReset()
427 phosphor::logging::entry("EXCEPTION=%s", e.what())); in ipmiOEMGetBMCResetDisables()
997 phosphor::logging::entry("ERROR=%s", e.what())); in ipmiOEMGetProcessorErrConfig()
1062 phosphor::logging::entry("EXCEPTION=%s", e.what())); in ipmiOEMSetProcessorErrConfig()
1704 phosphor::logging::entry("ERR=%s", e.what())); in getFanProfileInterface()
1790 phosphor::logging::entry("EXCEPTION=%s", e.what())); in ipmiOEMSetFanConfig()
1931 phosphor::logging::entry("ERR=%s", e.what())); in getPidConfigs()
2085 phosphor::logging::entry("ERR=%s", e.what())); in ipmiOEMSetFscParameter()
2270 phosphor::logging::entry("ERR=%s", e.what())); in ipmiOEMGetFscParameter()
2936 phosphor::logging::entry("ERR=%s", e.what())); in ipmiOEMReadBoardProductId()
[all …]
|
| /openbmc/linux/sound/pci/ |
| H A D | ens1370.c | 795 unsigned int what = 0; in snd_ensoniq_trigger() local
799 what |= ES_P1_PAUSE; in snd_ensoniq_trigger()
802 what |= ES_P2_PAUSE; in snd_ensoniq_trigger()
809 ensoniq->sctrl |= what; in snd_ensoniq_trigger()
811 ensoniq->sctrl &= ~what; in snd_ensoniq_trigger()
819 unsigned int what = 0; in snd_ensoniq_trigger() local
823 what |= ES_DAC1_EN; in snd_ensoniq_trigger()
826 what |= ES_DAC2_EN; in snd_ensoniq_trigger()
829 what |= ES_ADC_EN; in snd_ensoniq_trigger()
835 ensoniq->ctrl |= what; in snd_ensoniq_trigger()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | README.md | 83 the request would be ambiguous and probably not what the user wanted.
86 (while leaving the second chassis on) is certainly _not_ what the API user had
96 them would _not_ be what the API user intended.
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | writing-schema.rst | 42 information about this binding. It should contain things such as what the block
85 vocabulary for that property. The properties schemas are what are used for
89 binding schema need to be defined such as how many values are valid or what
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | boot-time-mm.rst | 36 descriptions for the internal functions can help to understand what
|
| H A D | tracepoint.rst | 23 the available tracepoints. The intention is to understand not only what
|
| /openbmc/linux/drivers/pps/ |
| H A D | Kconfig | 30 problem with PPS support and want to see more of what is going on.
|
| /openbmc/linux/drivers/usb/serial/ |
| H A D | whiteheat.h | 159 __u8 what; /* bit pattern of what to purge */ member
|
| /openbmc/u-boot/doc/device-tree-bindings/nand/ |
| H A D | nvidia,tegra20-nand.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | rule_tests.cpp | 73 EXPECT_STREQ(error.what(), "Communication error"); in TEST()
|