Home
last modified time | relevance | path

Searched full:period (Results 1 – 25 of 2664) sorted by relevance

12345678910>>...107

/openbmc/phosphor-led-manager/configs/
H A Dcom.ibm.Hardware.Chassis.Model.Rainier4U.json10 "Period": 1000, number
22 "Period": 0, number
34 "Period": 0, number
46 "Period": 0, number
58 "Period": 0, number
65 "Period": 0, number
72 "Period": 0, number
84 "Period": 0, number
91 "Period": 0, number
98 "Period": 0, number
[all …]
H A Dcom.ibm.Hardware.Chassis.Model.Everest.json10 "Period": 1000, number
22 "Period": 0, number
34 "Period": 0, number
46 "Period": 0, number
58 "Period": 0, number
65 "Period": 0, number
72 "Period": 0, number
84 "Period": 0, number
91 "Period": 0, number
98 "Period": 0, number
[all …]
H A Dcom.ibm.Hardware.Chassis.Model.Rainier1S4U.json10 "Period": 1000, number
22 "Period": 0, number
34 "Period": 0, number
46 "Period": 0, number
58 "Period": 0, number
65 "Period": 0, number
72 "Period": 0, number
84 "Period": 0, number
91 "Period": 0, number
98 "Period": 0, number
[all …]
H A Dcom.ibm.Hardware.Chassis.Model.Rainier2U.json10 "Period": 1000, number
22 "Period": 0, number
34 "Period": 0, number
46 "Period": 0, number
58 "Period": 0, number
65 "Period": 0, number
72 "Period": 0, number
84 "Period": 0, number
91 "Period": 0, number
98 "Period": 0, number
[all …]
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/leds/gbs-led-manager-config/
H A Dled.yaml5 Period: 1000
12 Period: 1000
19 Period: 0
26 Period: 1000
32 Period: 1000
39 Period: 250
44 Period: 250
50 Period: 250
55 Period: 250
61 Period: 250
[all …]
/openbmc/openbmc/meta-ieisystem/meta-nf5280m7/recipes-phosphor/leds/phosphor-led-manager/
H A Dled-group-config.json10 "Period": 1000, number
22 "Period": 0, number
34 "Period": 1000, number
46 "Period": 0, number
58 "Period": 1000, number
70 "Period": 0, number
82 "Period": 1000, number
89 "Period": 1000, number
96 "Period": 0, number
108 "Period": 0, number
[all …]
/openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/leds/romulus-led-manager-config/
H A Dled.yaml5 Period: 1000
12 Period: 0
19 Period: 0
26 Period: 1000
37 Period: 1000
48 Period: 0
54 Period: 0
60 Period: 0
66 Period: 0
72 Period: 0
[all …]
/openbmc/openbmc/meta-ieisystem/meta-fp5280g3/recipes-phosphor/leds/phosphor-led-manager/
H A Dled-group-config.json10 "Period": 1000, number
17 "Period": 0, number
29 "Period": 1000, number
36 "Period": 0, number
56 "Period": 1000, number
68 "Period": 0, number
80 "Period": 1000, number
92 "Period": 0, number
104 "Period": 1000, number
111 "Period": 1000, number
[all …]
/openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/leds/ethanolx-led-manager-config/
H A Dled.yaml7 Period: 0
14 Period: 1000
21 Period: 1000
32 Period: 0
38 Period: 0
44 Period: 0
50 Period: 0
56 Period: 0
62 Period: 0
68 Period: 0
[all …]
/openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/leds/daytonax-led-manager-config/
H A Dled.yaml7 Period: 0
14 Period: 1000
21 Period: 1000
32 Period: 0
38 Period: 0
44 Period: 0
50 Period: 0
56 Period: 0
62 Period: 0
68 Period: 0
[all …]
/openbmc/linux/lib/
H A Dflex_proportions.c3 * Floating proportions with flexible aging period
14 * Where x_{i,j} is j's number of events in i-th last time period and x_i is
15 * total number of events in i-th last time period.
26 * When a new period is declared, we could do:
33 * occurs. This can bit trivially implemented by remembering last period in
42 p->period = 0; in fprop_global_init()
57 * Declare @periods new periods. It is upto the caller to make sure period
79 p->period += periods; in fprop_new_period()
93 pl->period = 0; in fprop_local_init_single()
105 unsigned int period = p->period; in fprop_reflect_period_single() local
[all …]
/openbmc/openbmc/meta-ampere/meta-mitchell/recipes-phosphor/leds/phosphor-led-manager/
H A Dcom.ampere.Hardware.Chassis.Model.MtMitchell.json10 "Period": 0, number
17 "Period": 2000, number
34 "Period": 1000, number
46 "Period": 1000, number
58 "Period": 1000, number
65 "Period": 1000, number
77 "Period": 1000, number
84 "Period": 1000, number
96 "Period": 1000, number
103 "Period": 1000, number
[all …]
/openbmc/linux/drivers/iio/common/inv_sensors/
H A Dinv_sensors_timestamp.c46 /* save chip parameters and compute min and max clock period */ in inv_sensors_timestamp_init()
51 /* current multiplier and period values after reset */ in inv_sensors_timestamp_init()
53 ts->period = chip->init_period; in inv_sensors_timestamp_init()
55 /* use theoretical value for chip period */ in inv_sensors_timestamp_init()
61 uint32_t period, bool fifo) in inv_sensors_timestamp_update_odr() argument
69 mult = period / ts->chip.clock_period; in inv_sensors_timestamp_update_odr()
81 static bool inv_validate_period(struct inv_sensors_timestamp *ts, uint32_t period, uint32_t mult) in inv_validate_period() argument
85 /* check that period is acceptable */ in inv_validate_period()
88 if (period > period_min && period < period_max) in inv_validate_period()
95 uint32_t mult, uint32_t period) in inv_update_chip_period() argument
[all …]
/openbmc/linux/drivers/gpu/drm/tegra/
H A Dmipi-phy.c17 unsigned long period) in mipi_dphy_timing_get_default() argument
20 timing->clkpost = 70 + 52 * period; in mipi_dphy_timing_get_default()
30 timing->hsprepare = 65 + 5 * period; in mipi_dphy_timing_get_default()
31 timing->hszero = 145 + 5 * period; in mipi_dphy_timing_get_default()
32 timing->hssettle = 85 + 6 * period; in mipi_dphy_timing_get_default()
39 * T_HS-TRAIL = max(n * 8 * period, 60 + n * 4 * period) in mipi_dphy_timing_get_default()
43 * not parameterize on anything other that period, so this code will in mipi_dphy_timing_get_default()
46 timing->hstrail = max(4 * 8 * period, 60 + 4 * 4 * period); in mipi_dphy_timing_get_default()
63 unsigned long period) in mipi_dphy_timing_validate() argument
68 if (timing->clkpost < (60 + 52 * period)) in mipi_dphy_timing_validate()
[all …]
/openbmc/linux/drivers/pwm/
H A Dpwm-microchip-core.c17 * As setting the period/duty cycle takes 4 register writes, there is a window
18 * in which this races against the start of a new period.
23 * period. Therefore to get a 0% waveform, the output is set the max high/low
25 * If the duty cycle is 0%, and the requested period is less than the
26 * available period resolution, this will manifest as a ~100% waveform (with
28 * - The PWM period is set for the whole IP block not per channel. The driver
29 * will only change the period if no other PWM output is enabled.
60 struct mutex lock; /* protects the shared period */
72 bool enable, u64 period) in mchp_core_pwm_enable() argument
95 * applied to the waveform at the beginning of the next period. in mchp_core_pwm_enable()
[all …]
H A Dpwm-visconti.c15 * running period is completed. This way the hardware switches atomically
17 * - Disabling the hardware completes the currently running period and keeps
50 u32 period, duty_cycle, pwmc0; in visconti_pwm_apply() local
58 * The biggest period the hardware can provide is in visconti_pwm_apply()
63 if (state->period > (0xffff << 3) * 1000) in visconti_pwm_apply()
64 period = (0xffff << 3) * 1000; in visconti_pwm_apply()
66 period = state->period; in visconti_pwm_apply()
68 if (state->duty_cycle > period) in visconti_pwm_apply()
69 duty_cycle = period; in visconti_pwm_apply()
78 period /= 1000; in visconti_pwm_apply()
[all …]
/openbmc/linux/Documentation/RCU/Design/Expedited-Grace-Periods/
H A DExpedited-Grace-Periods.rst17 Expedited Grace Period Design
23 grace period.
32 state, the expedited grace period has completed.
43 expedited grace period is shown in the following diagram:
54 Otherwise, the expedited grace period will use
72 block the current expedited grace period until it resumes and finds its
75 the CPU is no longer blocking the grace period.
86 | Why not just have the expedited grace period check the state of all |
116 the handling of a given CPU by an RCU-sched expedited grace period is
137 Expedited Grace Period and CPU Hotplug
[all …]
/openbmc/linux/Documentation/RCU/Design/Memory-Ordering/
H A DTree-RCU-Memory-Ordering.rst2 A Tour Through TREE_RCU's Grace-Period Memory Ordering
13 grace-period memory ordering guarantee is provided.
15 What Is Tree RCU's Grace Period Memory Ordering Guarantee?
20 Any code that happens after the end of a given RCU grace period is guaranteed
22 period that are within RCU read-side critical sections.
24 period is guaranteed to not see the effects of all accesses following the end
25 of that grace period that are within RCU read-side critical sections.
34 two phases, one of which is executed before the grace period and
35 the other of which is executed after the grace period.
46 Tree RCU Grace Period Memory Ordering Building Blocks
[all …]
/openbmc/qemu/util/
H A Dtimed-average.c36 * - Create two windows with a certain expiration period, and
37 * offsetted by period / 2.
57 * @period: the expiration period in nanoseconds
60 int64_t period) in update_expiration() argument
63 int64_t elapsed = (now - w->expiration) % period; in update_expiration()
65 int64_t remaining = period - elapsed; in update_expiration()
97 * @period: the time window period in nanoseconds
100 uint64_t period) in timed_average_init() argument
105 * the interval [ta->period/2,ta->period). By adjusting the in timed_average_init()
106 * requested period by 4/3, we guarantee that they're in the in timed_average_init()
[all …]
/openbmc/openbmc/meta-ampere/meta-jefferson/recipes-phosphor/leds/phosphor-led-manager/
H A Dcom.ampere.Hardware.Chassis.Model.MtJefferson.json10 "Period": 0, number
17 "Period": 2000, number
34 "Period": 1000, number
46 "Period": 1000, number
58 "Period": 1000, number
70 "Period": 1000, number
82 "Period": 1000, number
94 "Period": 1000, number
106 "Period": 1000, number
118 "Period": 1000, number
[all …]
/openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/leds/phosphor-led-manager/
H A Dcom.ampere.Hardware.Chassis.Model.MtJade.json20 "Period": 0, number
33 "Period": 1000 number
45 "Period": 1000 number
57 "Period": 1000 number
69 "Period": 1000 number
81 "Period": 1000 number
93 "Period": 1000 number
105 "Period": 1000 number
117 "Period": 1000 number
129 "Period": 1000 number
[all …]
/openbmc/qemu/hw/core/
H A Dptimer.c28 int64_t period; member
54 uint64_t period; in ptimer_reload() local
79 period = s->period; in ptimer_reload()
86 if (s->period == 0 && s->period_frac == 0) { in ptimer_reload()
88 fprintf(stderr, "Timer with period zero, disabling\n"); in ptimer_reload()
141 if (s->enabled == 1 && (delta * period < 10000) && in ptimer_reload()
143 period = 10000 / delta; in ptimer_reload()
148 s->next_event = s->last_event + delta * period; in ptimer_reload()
223 uint64_t period = s->period; in ptimer_get_count() local
225 if (!oneshot && (s->delta * period < 10000) && in ptimer_get_count()
[all …]
H A Dclock.c57 bool clock_set(Clock *clk, uint64_t period) in clock_set() argument
59 if (clk->period == period) { in clock_set()
62 trace_clock_set(CLOCK_PATH(clk), CLOCK_PERIOD_TO_HZ(clk->period), in clock_set()
63 CLOCK_PERIOD_TO_HZ(period)); in clock_set()
64 clk->period = period; in clock_set()
72 * Return the period to be used for child clocks, which is the parent in clock_get_child_period()
73 * clock period adjusted for multiplier and divider effects. in clock_get_child_period()
75 return muldiv64(clk->period, clk->multiplier, clk->divider); in clock_get_child_period()
95 if (child->period != child_period) { in clock_propagate_period()
99 child->period = child_period; in clock_propagate_period()
[all …]
/openbmc/qemu/include/hw/
H A Dclock.h32 ClockUpdate = 1, /* Clock period has just updated */
33 ClockPreUpdate = 2, /* Clock period is about to update */
39 * clock store a value representing the clock's period in 2^-32ns unit.
60 * @period: unsigned integer representing the period of the clock
78 uint64_t period; member
157 * Setup @src as the clock source of @clk. The current @src period
184 * Set the local cached period value of @clk to @value.
204 * Propagate the clock period that has been previously configured using
242 * @return: the current period.
246 return clk->period; in clock_get()
[all …]
/openbmc/linux/include/linux/iio/common/
H A Dinv_sensors_timestamp.h11 * @clock_period: internal clock period in ns
13 * @init_period: chip initial period at reset in ns
46 * @min_period: minimal acceptable clock period
47 * @max_period: maximal acceptable clock period
50 * @mult: current internal period multiplier
51 * @new_mult: new set internal period multiplier (not yet effective)
52 * @period: measured current period of the sensor
53 * @chip_period: accumulator for computing internal chip period
63 uint32_t period; member
71 uint32_t period, bool fifo);
[all …]

12345678910>>...107