Home
last modified time | relevance | path

Searched full:reprogram (Results 1 – 25 of 143) sorted by relevance

123456

/linux-6.14.4/drivers/mtd/maps/
DKconfig168 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
206 as an MTD device - with this you can reprogram your BIOS.
215 as an MTD device - with this you can reprogram your BIOS.
224 as an MTD device - with this you can reprogram your BIOS.
233 as an MTD device - with this you can reprogram your BIOS.
242 as an MTD device - with this you can reprogram your BIOS.
269 as an MTD device - with this you can reprogram your BIOS.
Dsc520cdp.c187 ** ROMCS0, ROMCS1 and BOOTCS. Reprogram each of these with a in sc520cdp_setup_par()
193 /* if target device field matches, reprogram the PAR */ in sc520cdp_setup_par()
219 /* reprogram PAR registers so flash appears at the desired addresses */ in init_sc520cdp()
/linux-6.14.4/sound/pci/ctxfi/
Dcttimer.c54 unsigned int reprogram:1; /* need to reprogram the internval */ member
172 * reprogram the timer interval;
188 atimer->reprogram = 0; /* clear flag */ in ct_xfitimer_reprogram()
224 atimer->reprogram = 0; /* clear flag */ in ct_xfitimer_reprogram()
258 } while (atimer->reprogram); in ct_xfitimer_callback()
279 atimer->reprogram = 1; in ct_xfitimer_update()
/linux-6.14.4/kernel/time/
Dhrtimer.c196 * to queue, then a remote reprogram is necessary. However there is no
221 * elected new base. An IPI will we issued to reprogram in hrtimer_suitable_target()
688 * T1 is removed, so this code is called and would reprogram in __hrtimer_reprogram()
690 * will not reprogram the hardware due to hang_detected being in __hrtimer_reprogram()
701 * Reprogram the event source with checking both queues for the
822 static void hrtimer_reprogram(struct hrtimer *timer, bool reprogram) in hrtimer_reprogram() argument
857 !reprogram) in hrtimer_reprogram()
862 * If the timer is not on the current cpu, we cannot reprogram in hrtimer_reprogram()
873 * clock bases and reprogram the clock event device. in hrtimer_reprogram()
951 * also requires to eventually reprogram the per CPU clock event devices
[all …]
Dtick-broadcast.c750 * Two reasons for reprogram: in tick_handle_oneshot_broadcast()
837 * We only reprogram the broadcast timer if we in ___tick_broadcast_oneshot_control()
873 * handler. No need to reprogram the timer in ___tick_broadcast_oneshot_control()
892 * reached, we would reprogram the cpu local in ___tick_broadcast_oneshot_control()
923 * We got woken by something else. Reprogram in ___tick_broadcast_oneshot_control()
1167 * Detect this condition and reprogram the cpu local timer in hotplug_cpu__broadcast_tick_pull()
Dclockevents.c296 * clockevents_program_event - Reprogram the clock event device.
537 * clockevents_update_freq - Update frequency and reprogram a clock event device.
541 * Reconfigure and reprogram a clock event device in oneshot
/linux-6.14.4/drivers/mmc/core/
Dcrypto.c17 /* Reset might clear all keys, so reprogram all the keys. */ in mmc_crypto_set_initial_state()
/linux-6.14.4/kernel/sched/
Didle.c280 * doesn't tell about pending needed timer reprogram. in do_idle()
297 * instruction. This can leak a pending needed timer reprogram. in do_idle()
303 * again to reprogram the tick. in do_idle()
/linux-6.14.4/drivers/ufs/core/
Dufshcd-crypto.c104 * Reprogram the keyslots if needed, and return true if CRYPTO_GENERAL_ENABLE
112 /* Reset might clear all keys, so reprogram all the keys. */ in ufshcd_crypto_enable()
/linux-6.14.4/Documentation/devicetree/bindings/clock/
Dsilabs,si5341.txt58 - silabs,reprogram: When present, the driver will always assume the device must
119 silabs,reprogram; /* Chips are not programmed, always reset */
/linux-6.14.4/Documentation/userspace-api/media/v4l/
Ddev-mem2mem.rst27 the hardware and reprogram it whenever another file handler gets access.
/linux-6.14.4/drivers/clk/imx/
Dclk-cpu.c52 /* reprogram PLL */ in clk_cpu_set_rate()
/linux-6.14.4/Documentation/security/
Dsak.rst36 And that's it! Only the superuser may reprogram the SAK key.
/linux-6.14.4/Documentation/misc-devices/
Dc2port.rst28 By using this driver you can reprogram the in-system flash without EC2
/linux-6.14.4/Documentation/devicetree/bindings/fpga/
Dfpga-region.yaml140 The intended use is that a Device Tree overlay (DTO) can be used to reprogram an
146 and adds the "firmware-name" property is taken as a request to reprogram the
/linux-6.14.4/Documentation/devicetree/bindings/net/
Dmscc-phy-vsc8531.txt16 by being able to reprogram drive strength
/linux-6.14.4/arch/mips/kernel/
Dspram.c148 /* reprogram the base address base address and enable */ in probe_spram()
/linux-6.14.4/drivers/cpufreq/
Dimx6q-cpufreq.c111 * reprogram PLL for frequency scaling. The procedure of reprogramming in imx6q_set_target()
117 * - Reprogram pll1_sys_clk and reparent pll1_sw_clk back to it in imx6q_set_target()
/linux-6.14.4/drivers/acpi/
Dsleep.c618 /* Reprogram control registers */ in acpi_suspend_enter()
943 /* Reprogram control registers */ in acpi_hibernation_enter()
957 /* Reprogram control registers */ in acpi_hibernation_leave()
/linux-6.14.4/drivers/fpga/
Ddfl-n3000-nios.c321 * card, we need to reprogram a new Nios firmware via the BMC chip on in n3000_nios_init_done_check()
395 * reprogram a new Nios firmware and restore the card. So the in n3000_nios_init_done_check()
Dfpga-region.c93 * reprogram the region.
/linux-6.14.4/sound/hda/
Dhdac_i915.c21 * snd_hdac_i915_set_bclk - Reprogram BCLK for HSW/BDW
/linux-6.14.4/drivers/ata/
Dpata_cmd640.c125 * Channel 1 has shared timings. We must reprogram the
/linux-6.14.4/arch/m68k/coldfire/
Dm53xx.c512 * The device must be put into LIMP mode to reprogram the PLL. in clock_pll()
518 /* Reprogram PLL for desired fsys */ in clock_pll()
/linux-6.14.4/drivers/gpu/drm/i915/display/
Dintel_dpt.c191 * transitions, so here we reprogram the PTE entries in those tables.

123456