| /linux/Documentation/devicetree/bindings/power/supply/ |
| H A D | richtek,rt5033-charger.yaml | 26 Current of pre-charge mode. The pre-charge current levels are 350 mA 27 to 650 mA programmed by I2C per 100 mA. 30 Current of fast-charge mode. The fast-charge current levels are 700 mA 31 to 2000 mA programmed by I2C per 100 mA. 34 This property is end of charge current. Its level ranges from 150 mA 35 to 600 mA. Between 150 mA and 300 mA in 50 mA steps, between 300 mA and 36 600 mA in 100 mA steps.
|
| H A D | ti,lp8727.yaml | 53 0 = 90mA, 1 = 100mA, 2 = 400mA, 3 = 450mA, 4 = 500mA, 5 = 600mA, 54 6 = 700mA, 7 = 800mA, 8 = 900mA, 9 = 1000mA 76 /* AC charger: 5% EOC and 500mA charging current */ 83 /* USB charger: 10% EOC and 400mA charging current */
|
| /linux/Documentation/devicetree/bindings/leds/ |
| H A D | richtek,rt8515.yaml | 63 maximum current of 700mA. By setting this attribute in 75 maximum current of 700mA. By setting this attribute in
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | cs35l36.txt | 18 - cirrus,boost-peak-milliamp : Boost-converter peak current limit in mA. 20 Range starts at 1600mA and goes to a maximum of 4500mA with increments of 21 50mA. 75 weak-FET operation. The range is 50mV to 700mV in 50mV increments.
|
| /linux/drivers/power/supply/ |
| H A D | adp5061.c | 82 #define ADP5061_ICHG_MAX 1300 // mA 120 700, 750, 800, 850, 900, 950, 1000, 1050, 1100, 1200, 1300, 131 100, 150, 200, 250, 300, 400, 500, 600, 700, 195 /* Convert from uA to mA */ in adp5061_set_input_current_limit() 319 /* Convert from uA to mA */ in adp5061_set_const_chg_current() 374 /* Convert from uA to mA */ in adp5061_set_prechg_current()
|
| /linux/Documentation/translations/it_IT/doc-guide/ |
| H A D | sphinx.rst | 26 e formato speciale, ma a parte questo vengono processati come reStructuredText. 30 nel tempo, in formato reStructuredText, ma la maggior parte di questi rimarranno 44 La maggior parte delle distribuzioni Linux forniscono Sphinx, ma l'insieme dei 86 grado di procedere anche se questi pacchetti non sono installati, ma il 192 quella che state leggendo ora), ma per una documentazione più elaborata è 280 Il nome della funzione (per esempio ioctl) rimane nel testo ma il nome del suo 302 ma con delle funzionalità aggiuntive: 498 version="1.1" baseProfile="full" width="70px" height="40px" viewBox="0 0 700 400">
|
| /linux/arch/mips/cavium-octeon/executive/ |
| H A D | cvmx-helper-xaui.c | 21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA 72 * Due to errata GMX-700 on CN56XXp1.x and CN52XXp1.x, the in __cvmx_helper_xaui_probe()
|
| H A D | cvmx-helper-sgmii.c | 21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA 347 * Due to errata GMX-700 on CN56XXp1.x and CN52XXp1.x, the in __cvmx_helper_sgmii_probe()
|
| /linux/Documentation/translations/it_IT/kernel-hacking/ |
| H A D | locking.rst | 99 funzioni a questo scopo. E poi ci sono quelle meno buone, ma farò finta 120 ma potreste bloccarvi trattenendolo. Se non potete trattenere un mutex 139 Se il kernel è compilato senza ``CONFIG_SMP`` ma con ``CONFIG_PREEMPT``, 161 ma questa dovrebbe essere evitata perché non ritorna in caso di segnali. 302 Condividere dati fra due gestori di interruzione hardware è molto raro, ma se 330 processore alla volta, ma se deve condividere dati con un altro thread, allora 381 contesto, ma come spin_lock(): dovete disabilitare i contesti che 717 non trattiene un riferimento per se, ma diventa più complicato. 911 può succedere anche con un solo processore (Ma non sui sistemi 971 Gli stalli sono un problema, ma non così terribile come la corruzione dei dati. [all …]
|
| /linux/drivers/scsi/isci/ |
| H A D | phy.c | 20 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA. 73 #define SCIC_SDS_PHY_MAX_ARBITRATION_WAIT_TIME (700) 297 /* Program the max ARB time for the PHY to 700us so we in sci_phy_link_layer_initialization()
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | sm8250.dtsi | 278 cpu7: cpu@700 { 5170 drive-strength = <2>; /* 2 mA */ 5179 drive-strength = <2>; /* 2 mA */ 5189 drive-strength = <2>; /* 2 mA */ 5198 drive-strength = <2>; /* 2 mA */ 5210 drive-strength = <2>; /* 2 mA */ 5219 drive-strength = <2>; /* 2 mA */ 5230 drive-strength = <2>; /* 2 mA */ 5239 drive-strength = <2>; /* 2 mA */
|
| H A D | sdm845.dtsi | 268 cpu7: cpu@700 { 2814 drive-strength = <2>; /* 2 mA */ 2822 drive-strength = <2>; /* 2 mA */ 2832 drive-strength = <2>; /* 2 mA */ 2840 drive-strength = <2>; /* 2 mA */ 4887 * Look ma, no clocks! The GPU clocks and power are
|
| /linux/drivers/video/fbdev/sis/ |
| H A D | init.h | 23 * * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA 1287 {1040, 700,1040, 700},
|
| H A D | 310vtbl.h | 23 * * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA 1071 {1040, 700,1040, 700},
|
| H A D | init301.c | 27 * * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA 3817 if (SiS_Pr->SiS_VGAVDE == 350) tempbx = 700; in SiS_GetCRT2Data301() 9092 /* The Chrontel 700x is connected to the 630/730 via 9112 … temp = SiS_WriteDDC2Data(SiS_Pr, (reg | myor)); /* Write RAB (700x: set bit 7, see datasheet) */ in SiS_SetChReg() 9123 /* Write to Chrontel 700x */ 9185 … temp = SiS_WriteDDC2Data(SiS_Pr,SiS_Pr->SiS_DDC_ReadAddr | myor); /* Write RAB (700x: | 0x80) */ in SiS_GetChReg() 9198 /* Read from Chrontel 700x */
|
| /linux/drivers/media/dvb-frontends/drx39xyj/ |
| H A D | drxj.c | 49 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. 936 700, /* NICAM */ 3693 /* io_pad_cfg_drive is set to power 2 (23 mA) */ in ctrl_uio_write() 3732 /* io_pad_cfg_drive is set to power 2 (23 mA) */ in ctrl_uio_write() 3771 /* io_pad_cfg_drive is set to power 2 (23 mA) */ in ctrl_uio_write() 3811 /* io_pad_cfg_drive is set to power 2 (23 mA) */ in ctrl_uio_write()
|
| /linux/drivers/media/dvb-frontends/ |
| H A D | drxk_hard.c | 71 #define DEFAULT_DRXK_MPEG_LOCK_TIMEOUT 700 540 /* io_pad_cfg_drive is set to power 2 (23 mA) */ in init_state()
|
| /linux/ |
| H A D | MAINTAINERS | 1282 M: Min Ma <mamin506@gmail.com> 5842 W: https://developer.arm.com/products/system-ip/trustzone-cryptocell/cryptocell-700-family 5849 W: https://developer.arm.com/products/system-ip/trustzone-cryptocell/cryptocell-700-family
|