Home
last modified time | relevance | path

Searched refs:saw (Results 1 – 25 of 45) sorted by relevance

12

/openbmc/linux/drivers/misc/lkdtm/
H A Dheap.c93 int *base, *val, saw; in lkdtm_READ_AFTER_FREE() local
123 saw = base[offset]; in lkdtm_READ_AFTER_FREE()
124 if (saw != *val) { in lkdtm_READ_AFTER_FREE()
126 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_AFTER_FREE()
158 int saw, *val; in lkdtm_READ_BUDDY_AFTER_FREE() local
180 saw = base[0]; in lkdtm_READ_BUDDY_AFTER_FREE()
181 if (saw != *val) { in lkdtm_READ_BUDDY_AFTER_FREE()
183 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_BUDDY_AFTER_FREE()
/openbmc/qemu/scripts/
H A Dget_maintainer.pl1964 my %saw;
1965 @parms = grep(!$saw{$_}++, @parms);
1972 my %saw;
1974 @parms = grep(!$saw{$_}++, @parms);
2025 my %saw;
2029 if (!$saw{$address}) {
2035 $saw{$address} = 1;
/openbmc/linux/arch/arm64/boot/dts/qcom/
H A Dmsm8996-xiaomi-common.dtsi647 qcom,saw-reg = <&saw3>;
649 qcom,saw-slave;
652 qcom,saw-slave;
655 qcom,saw-slave;
658 qcom,saw-leader;
H A Dmsm8996-oneplus-common.dtsi259 qcom,saw-reg = <&saw3>;
262 qcom,saw-slave;
266 qcom,saw-slave;
270 qcom,saw-leader;
H A Dmsm8996-sony-xperia-tone.dtsi590 qcom,saw-reg = <&saw3>;
593 qcom,saw-slave;
597 qcom,saw-slave;
601 qcom,saw-leader;
H A Dmsm8939.dtsi51 qcom,saw = <&saw0>;
69 qcom,saw = <&saw1>;
82 qcom,saw = <&saw2>;
95 qcom,saw = <&saw3>;
107 qcom,saw = <&saw4>;
126 qcom,saw = <&saw5>;
139 qcom,saw = <&saw6>;
152 qcom,saw = <&saw7>;
H A Dapq8096-db820c.dts600 qcom,saw-reg = <&saw3>;
604 qcom,saw-slave;
607 qcom,saw-slave;
610 qcom,saw-leader;
H A Dmsm8916.dtsi127 qcom,saw = <&cpu0_saw>;
142 qcom,saw = <&cpu1_saw>;
157 qcom,saw = <&cpu2_saw>;
172 qcom,saw = <&cpu3_saw>;
/openbmc/linux/Documentation/devicetree/bindings/regulator/
H A Dqcom,spmi-regulator.yaml30 qcom,saw-reg:
96 qcom,saw-slave:
100 qcom,saw-leader:
/openbmc/openbmc/.github/ISSUE_TEMPLATE/
H A Dbug_report.md16 **Unexpected behavior you saw**
/openbmc/linux/tools/power/cpupower/
H A DTODO6 - Somewhere saw the ability to read power consumption of
/openbmc/linux/arch/arm/boot/dts/qcom/
H A Dqcom-ipq4019.dtsi52 qcom,saw = <&saw0>;
66 qcom,saw = <&saw1>;
80 qcom,saw = <&saw2>;
94 qcom,saw = <&saw3>;
106 qcom,saw = <&saw_l2>;
H A Dqcom-apq8084.dtsi37 qcom,saw = <&saw0>;
48 qcom,saw = <&saw1>;
59 qcom,saw = <&saw2>;
70 qcom,saw = <&saw3>;
78 qcom,saw = <&saw_l2>;
H A Dqcom-msm8960.dtsi30 qcom,saw = <&saw0>;
40 qcom,saw = <&saw1>;
H A Dqcom-msm8974.dtsi43 qcom,saw = <&saw0>;
54 qcom,saw = <&saw1>;
65 qcom,saw = <&saw2>;
76 qcom,saw = <&saw3>;
84 qcom,saw = <&saw_l2>;
H A Dqcom-apq8064.dtsi46 qcom,saw = <&saw0>;
57 qcom,saw = <&saw1>;
68 qcom,saw = <&saw2>;
79 qcom,saw = <&saw3>;
/openbmc/u-boot/scripts/
H A Dget_maintainer.pl2373 my %saw;
2374 @parms = grep(!$saw{$_}++, @parms);
2381 my %saw;
2383 @parms = grep(!$saw{$_}++, @parms);
2434 my %saw;
2438 if (!$saw{$address}) {
2444 $saw{$address} = 1;
/openbmc/linux/scripts/
H A Dget_maintainer.pl2438 my %saw;
2439 @parms = grep(!$saw{$_}++, @parms);
2446 my %saw;
2448 @parms = grep(!$saw{$_}++, @parms);
2499 my %saw;
2503 if (!$saw{$address}) {
2509 $saw{$address} = 1;
/openbmc/linux/Documentation/devicetree/bindings/soc/qcom/
H A Dqcom,spm.yaml58 qcom,saw = <&saw0>;
/openbmc/linux/drivers/eisa/
H A DKconfig18 the older ISA bus. The EISA bus saw limited use between 1988 and
/openbmc/openbmc/poky/meta/recipes-devtools/rust/
H A Drust-cross-canadian.inc43 # in those paths and we hit symbol errors. We saw particular problems with symbol
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-devices-aer_stats10 saw any problems).
/openbmc/linux/sound/pci/cs46xx/
H A Dcs46xx_dsp_scb_types.h39 u32 saw; /* Source Address Word */ member
/openbmc/linux/Documentation/scheduler/
H A Dsched-stats.rst11 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
/openbmc/linux/Documentation/RCU/
H A DRTFP.txt91 1995 also saw the first publication of DYNIX/ptx's RCU mechanism
102 The year 2000 saw an email exchange that would likely have
104 [RustyRussell2000a,RustyRussell2000b]. Instead, 2001 saw the first
137 Later that year saw a paper describing an RCU implementation
154 2006 saw the first best-paper award for an RCU paper [ThomasEHart2006a],
162 2007 saw the journal version of the award-winning RCU paper from 2006
170 2008 saw a journal paper on real-time RCU [DinakarGuniguntala2008IBMSysJ],
1436 like it, but time he saw an opportunity for this technique,

12