Home
last modified time | relevance | path

Searched full:trm (Results 1 – 25 of 169) sorted by relevance

1234567

/Linux-v5.10/Documentation/devicetree/bindings/pinctrl/
Dnvidia,tegra20-pinmux.txt37 TRM to determine which are valid for each pin or group.
48 or "LPMD1" and "LPMD0" in the Tegra TRM.
51 Tegra TRM.
54 Tegra TRM.
57 "DRVDN_SLWR" in the Tegra TRM.
60 "DRVUP_SLWF" in the Tegra TRM.
63 or groups. See the Tegra TRM and various pinmux spreadsheets for complete
Dnvidia,tegra210-pinmux.txt31 See the TRM to determine which properties and values apply to each pin/group.
68 Tegra TRM.
71 Tegra TRM.
74 "DRVDN_SLWR" in the Tegra TRM.
77 "DRVUP_SLWF" in the Tegra TRM.
Dnvidia,tegra194-pinmux.txt19 See the TRM to determine which properties and values apply to each pin/group.
53 Tegra TRM.
56 Tegra TRM.
/Linux-v5.10/Documentation/devicetree/bindings/bus/
Dti-sysc.txt60 Manual (TRM) for the interconnect target module
63 target module as documented in the TRM for SYSCONFIG
67 target module as documented in the TRM for SYSCONFIG
74 TRM for SYSSTATUS registers, typically 1 with some devices
87 optional clocks that can be specified as listed in TRM
/Linux-v5.10/Documentation/devicetree/bindings/clock/
Dnvidia,tegra124-dfll.txt40 - nvidia,droop-ctrl: See the register CL_DVFS_DROOP_CTRL in the TRM.
41 - nvidia,force-mode: See the field DFLL_PARAMS_FORCE_MODE in the TRM.
42 - nvidia,cf: Numeric value, see the field DFLL_PARAMS_CF_PARAM in the TRM.
43 - nvidia,ci: Numeric value, see the field DFLL_PARAMS_CI_PARAM in the TRM.
44 - nvidia,cg: Numeric value, see the field DFLL_PARAMS_CG_PARAM in the TRM.
47 - nvidia,cg-scale: Boolean value, see the field DFLL_PARAMS_CG_SCALE in the TRM.
/Linux-v5.10/Documentation/translations/zh_CN/video4linux/
Domap3isp.txt221 大多数域的解释可以在 OMAP 的 TRM 中找到。以下两个域对于以上所有的
222 私有 IOCTL 配置都很常见，由于他们没有在 TRM 中提及，故需要对其有
257 OMAP 3430 TRM:
261 OMAP 35xx TRM:
264 OMAP 3630 TRM:
268 DM 3730 TRM:
/Linux-v5.10/Documentation/admin-guide/media/
Domap3isp.rst74 OMAP 3430 TRM:
78 OMAP 35xx TRM:
81 OMAP 3630 TRM:
85 DM 3730 TRM:
/Linux-v5.10/drivers/bus/
Domap-ocp2scp.c48 * As per AM572x TRM: http://www.ti.com/lit/ug/spruhz6/spruhz6.pdf in omap_ocp2scp_probe()
50 * As per OMAP4430 TRM: http://www.ti.com/lit/ug/swpu231ap/swpu231ap.pdf in omap_ocp2scp_probe()
52 * As per OMAP4460 TRM: http://www.ti.com/lit/ug/swpu235ab/swpu235ab.pdf in omap_ocp2scp_probe()
54 * As per OMAP543x TRM http://www.ti.com/lit/pdf/swpu249 in omap_ocp2scp_probe()
/Linux-v5.10/Documentation/admin-guide/perf/
Darm-cmn.rst25 Most events are specified in a format based directly on the TRM
45 (as defined in the "Node ID Mapping" section of the TRM).
59 "wp_exclusive" are specified per the TRM definitions for dtm_wp_config0.
/Linux-v5.10/drivers/pinctrl/ti/
Dpinctrl-ti-iodelay.c31 * @signature_mask: CONFIG_REG mask for the signature bits (see TRM)
32 * @signature_value: CONFIG_REG signature value to be written (see TRM)
33 * @lock_mask: CONFIG_REG mask for the lock bits (see TRM)
34 * @lock_val: CONFIG_REG lock value for the lock bits (see TRM)
35 * @unlock_val:CONFIG_REG unlock value for the lock bits (see TRM)
36 * @binary_data_coarse_mask: CONFIG_REG coarse mask (see TRM)
37 * @binary_data_fine_mask: CONFIG_REG fine mask (see TRM)
86 * struct ti_iodelay_reg_values - Computed io_reg configuration values (see TRM)
197 * Update the configuration register as per TRM and lockup once done.
198 * *IMPORTANT NOTE* SoC TRM does recommend doing iodelay programmation only
/Linux-v5.10/drivers/firmware/
Dti_sci.h822 * For detailed information on the settings, see the UDMAP section of the TRM.
869 * For detailed information on the settings, see the UDMAP section of the TRM.
968 * section of the TRM for restrictions regarding this parameter.
1178 * section of the TRM for more information on this setting. Valid values for
1191 * See the UDMAP section of the TRM for more information on this setting.
1196 * See the UDMAP section of the TRM for more information on this setting.
1201 * See the UDMAP section of the TRM for more information on this setting.
1206 * See the UDMAP section of the TRM for more information on this setting.
1211 * the UDMAP section of the TRM for more information on this setting.
1216 * the UDMAP section of the TRM for more information on this setting.
[all …]
/Linux-v5.10/drivers/phy/ti/
Dphy-dm816x-usb.c30 * TRM has two sets of USB_CTRL registers.. The correct register bits
31 * are in TRM section 24.9.8.2 USB_CTRL Register. The TRM documents the
38 * according to the TRM. It's possible that USBPHY_CTRL is more generic,
Dphy-ti-pipe3.c215 /* DRA75x TRM Table 26-17 Preferred USB3_PHY_RX SCP Register Settings */
241 /* DRA75x TRM Table 26-9 Preferred SATA_PHY_RX SCP Register Settings */
251 .dig_hs_rate = 0, /* Not in TRM preferred settings */
252 .dig_ovrd_hs_rate = 0, /* Not in TRM preferred settings */
266 /* DRA75x TRM Table 26-62 Preferred PCIe_PHY_RX SCP Register Settings */
505 * as recommended in AM572x TRM SPRUHZ6, section 18.5.2.2, table in ti_pipe3_init()
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Dvexpress-sysreg.txt62 numbers - see motherboard's TRM for more details. All configuration
68 - compatible value : must be one of (corresponding to the TRM):
/Linux-v5.10/drivers/thermal/ti-soc-thermal/
Domap4xxx-bandgap.h57 * ADC conversion table limits. Ignore values outside the TRM listed
58 * range to avoid bogus thermal shutdowns. See omap4430 TRM chapter
/Linux-v5.10/arch/arm/boot/dts/
Domap3-gta04a5one.dts19 /* data lines, gpmc_d0..d7 not muxable according to TRM */
31 * according to TRM. OneNAND seems to require PIN_INPUT on clock.
Dam3517.dtsi36 * AM3517 TRM only lists 600MHz @ 1.2V, but omap36xx
159 /* Table Table 5-79 of the TRM shows 480ab000 is reserved */
/Linux-v5.10/arch/arm/mach-omap2/
Domap_hwmod_81xx_data.c34 * Common alwon .clkctrl_offs from dm814x TRM "Table 2-278. CM_ALWON REGISTERS"
35 * also dm816x TRM 18.7.17 CM_ALWON device register values minus 0x1400.
104 * TRM 18.7.6 CM_DEFAULT device register values minus 0x500
133 * L4 standard peripherals, see TRM table 1-12 for devices using this.
134 * See TRM table 1-73 for devices using the 125MHz SYSCLK6 clock.
144 * L4 high-speed peripherals. For devices using this, please see the TRM
145 * table 1-13. On dm816x, only EMAC, MDIO and SATA use this. See also TRM
Dprm2xxx_3xxx.h186 * check TRM if you are unsure
222 * 2420 TRM sometimes uses "EN_WAKEUP" instead of "EN_WKUP"
/Linux-v5.10/drivers/clk/davinci/
Dpsc-dm365.c72 * The TRM (ARM Subsystem User's Guide) shows two clocks input into
80 * Its not fully clear from TRM (ARM Subsystem User's Guide) as to what
/Linux-v5.10/drivers/staging/kpc2000/
Dkpc2000_spi.c125 unsigned int trm : 2; /* TxRx Mode */ member
280 sc.bitfield.trm = 0; in kp_spi_setup()
364 sc.bitfield.trm = KP_SPI_REG_CONFIG_TRM_TX; in kp_spi_transfer_one_message()
366 sc.bitfield.trm = KP_SPI_REG_CONFIG_TRM_RX; in kp_spi_transfer_one_message()
/Linux-v5.10/drivers/clk/ti/
Ddpll44xx.c21 * defined in OMAP4430/60 Public TRM section 3.6.3.3.2 "Enable Control,
87 * Public TRM section 3.6.3.3.2 "Enable Control, Status, and Low-Power
/Linux-v5.10/Documentation/devicetree/bindings/mmc/
Dsdhci-am654.yaml157 ti,trm-icp:
217 ti,trm-icp = <0x8>;
/Linux-v5.10/drivers/nvmem/
Dvf610-ocotp.c122 /* Refer section OTP read/write timing parameters in TRM */ in vf610_ocotp_calculate_timing()
183 * 0xBADABADA as mentioned by the TRM. We just read this in vf610_ocotp_read()
/Linux-v5.10/Documentation/devicetree/bindings/dma/
Dnvidia,tegra20-apbdma.txt16 select value for the peripheral. For more details, consult the Tegra TRM's

1234567