Home
last modified time | relevance | path

Searched +full:500 +full:ma (Results 1 – 25 of 74) sorted by relevance

123

/linux/Documentation/devicetree/bindings/power/supply/
H A Dti,lp8727.yaml53 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 */
H A Dbq24257.yaml59 of 500,000 is used (=500mA) instead.
H A Dbq2515x.yaml8 title: TI bq2515x 500-mA Linear charger family
H A Drichtek,rt9455.yaml55 Defaults to 500000 uA (500mA).
/linux/include/linux/power/
H A Dbq2415x_charger.h29 BQ2415X_MODE_NONE, /* unknown charger (100mA) */
30 BQ2415X_MODE_HOST_CHARGER, /* usb host/hub charger (500mA) */
36 int current_limit; /* mA */
39 int charge_current; /* mA */
40 int termination_current; /* mA */
/linux/drivers/media/dvb-frontends/
H A Dlnbp21.h31 0:Iout=500-650mA Isc=300mA
32 1:Iout=400-550mA Isc=200mA */
/linux/Documentation/devicetree/bindings/iio/addac/
H A Dadi,ad74115.yaml195 When not present, the DAC short-circuit current limit is 32mA in
196 either source or sink for VOUT and 4mA sink for IOUT.
197 When present, the limit is 16mA in either source or sink for VOUT,
198 1mA sink for IOUT.
212 enum: [250, 500, 750, 1000]
222 enum: [0, 50, 500, 1000, 10000]
237 enum: [0, 50, 500, 1000, 10000]
/linux/Documentation/devicetree/bindings/iio/dac/
H A Dadi,ad5755.yaml86 4: 4 mA to 20 mA current range.
87 5: 0 mA to 20 mA current range.
88 6: 0 mA to 24 mA current range.
108 - enum: [64000, 32000, 16000, 8000, 4000, 2000, 1000, 500, 250, 125, 64, 32, 16, 8, 4, 0]
/linux/arch/mips/include/asm/mach-rc32434/
H A Dprom.h25 * 675 Mass Ave, Cambridge, MA 02139, USA.
39 #define BOARD_RB532 "500"
40 #define BOARD_RB532A "500r5"
/linux/Documentation/devicetree/bindings/connector/
H A Dusb-connector.yaml103 USB 2.0 and USB 3.2 specifications, 5V 500mA for USB 2.0 ports and
104 5V 900mA or 1500mA for USB 3.2 ports in single-lane or dual-lane
237 5V@500mA) upon entering SNK_DISCOVERY(instead of 3A or the 1.5A, Rp current advertised, during
304 description: Indicates the preferred load step slew rate in mA/usec for
308 enum: [150, 500]
482 sink-bc12-completion-time-ms = <500>;
/linux/drivers/usb/phy/
H A Dphy.c19 #define DEFAULT_SDP_CUR_MAX 500
22 #define DEFAULT_DCP_CUR_MIN 500
220 * @mA: the current need to be set
231 void usb_phy_set_charger_current(struct usb_phy *usb_phy, unsigned int mA) in usb_phy_set_charger_current() argument
235 if (usb_phy->chg_cur.sdp_max == mA) in usb_phy_set_charger_current()
238 usb_phy->chg_cur.sdp_max = (mA > DEFAULT_SDP_CUR_MAX_SS) ? in usb_phy_set_charger_current()
239 DEFAULT_SDP_CUR_MAX_SS : mA; in usb_phy_set_charger_current()
242 if (usb_phy->chg_cur.dcp_max == mA) in usb_phy_set_charger_current()
245 usb_phy->chg_cur.dcp_max = (mA > DEFAULT_DCP_CUR_MAX) ? in usb_phy_set_charger_current()
246 DEFAULT_DCP_CUR_MAX : mA; in usb_phy_set_charger_current()
[all …]
/linux/drivers/mfd/
H A Dtps65010.c140 ? ((chgconfig & TPS_VBUS_500MA) ? 500 : 100) in dbg_chgconf()
413 if (tps->vbus == 500) in tps65010_work()
673 * 0 mA -- DON'T DRAW (might supply power instead)
674 * 100 mA -- usb unit load (slowest charge rate)
675 * 500 mA -- usb high power (fast battery charge)
677 int tps65010_set_vbus_draw(unsigned mA) in tps65010_set_vbus_draw() argument
686 if (mA >= 500) in tps65010_set_vbus_draw()
687 mA = 500; in tps65010_set_vbus_draw()
688 else if (mA >= 100) in tps65010_set_vbus_draw()
689 mA = 100; in tps65010_set_vbus_draw()
[all …]
/linux/drivers/input/touchscreen/
H A Dstmpe-ts.c59 * (0 -> 10 us, 1 -> 50 us, 2 -> 100 us, 3 -> 500 us,
63 * (0 -> 10 us, 1 -> 100 us, 2 -> 500 us, 3 -> 1 ms,
70 * (0 -> 20 mA typical 35 mA max, 1 -> 50 mA typical 80 mA max)
/linux/drivers/usb/gadget/
H A DKconfig100 int "Maximum VBUS Power usage (2-500 mA)"
101 range 2 500
110 milliAmperes. The permitted range of values is 2 - 500 mA;
111 0 mA would be legal, but can make some hosts misbehave.
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dmediatek,mt8365-pinctrl.yaml118 enum: [125, 250, 500, 1000]
126 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
127 can support 0.125/0.25/0.5/1mA adjustment. If we enable specific
130 When E1=0/E0=0, the strength is 0.125mA.
131 When E1=0/E0=1, the strength is 0.25mA.
132 When E1=1/E0=0, the strength is 0.5mA.
133 When E1=1/E0=1, the strength is 1mA.
H A Dmediatek,mt8192-pinctrl.yaml81 support 2/4/6/8/10/12/14/16mA in mt8192.
85 enum: [125, 250, 500, 1000]
/linux/Documentation/devicetree/bindings/leds/
H A Dleds-sgm3140.yaml7 title: SGMICRO SGM3140 500mA Buck/Boost Charge Pump LED Driver
/linux/include/linux/mfd/
H A Dtps65010.h25 * 675 Mass Ave, Cambridge, MA 02139, USA.
133 * 0 mA -- DON'T DRAW (might supply power instead)
134 * 100 mA -- usb unit load (slowest charge rate)
135 * 500 mA -- usb high power (fast battery charge)
137 extern int tps65010_set_vbus_draw(unsigned mA);
/linux/Documentation/devicetree/bindings/usb/
H A Dam33xx-usb.txt44 - mentor,power: Should be "500". This signifies the controller can supply up to
45 500mA when operating in host mode.
114 mentor,power = <500>;
160 mentor,power = <500>;
/linux/Documentation/devicetree/bindings/iio/afe/
H A Dtemperature-sense-rtd.yaml36 V 1mA
80 Common values are 100 for PT100, 500 for PT500, and 1000 for PT1000
/linux/drivers/power/supply/
H A Dadp5061.c81 #define ADP5061_ICHG_MAX 1300 // mA
118 50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650,
130 100, 150, 200, 250, 300, 400, 500, 600, 700,
194 /* Convert from uA to mA */ in adp5061_set_input_current_limit()
318 /* Convert from uA to mA */ in adp5061_set_const_chg_current()
373 /* Convert from uA to mA */ in adp5061_set_prechg_current()
H A Dwm8350_power.c97 /* make sure USB fast charge current is not > 500mA */ in wm8350_charger_config()
98 if (policy->fast_limit_USB_mA > 500) { in wm8350_charger_config()
99 dev_err(wm8350->dev, "USB fast charge > 500mA\n"); in wm8350_charger_config()
/linux/Documentation/translations/it_IT/process/
H A D5.Posting.rst28 Ma quando il lavoro è di una certa complessità, c'è molto da guadagnare
38 ma quelli che lo faranno penseranno di potervi aiutare a condurre il vostro
81 di lavoro significativa, ma, ripetiamolo ancora, generalmente sconsigliamo
115 per esempio), ma dovrebbero essere concettualmente piccole da permettere
135 - Però, non strafate. Una volta uno sviluppatore pubblicò una serie di 500
142 come una serie di patch, ma di lasciare questa infrastruttura inutilizzata
158 ma il lavoro non è davvero finito. Ogni patch deve essere preparata con
164 ma nel dubbio non fa di certo male aggiungerlo.
185 Scrivere un buon changelog è cruciale ma è spesso un'arte trascurata;
307 un luogo pubblico, ma gli indirizzi email usati lì sono privati; quindi non
H A D2.Process.rst62 consentita una modifica più consistente, ma tali occasioni sono rare.
97 rilevate nel precedente rilascio. Nessun baco è il benvenuto, ma quelli che
169 viene spesso svolto senza coinvolgere la comunità, ma è meglio renderlo
192 patch non riceve alcuna critica ma non è stata integrata dal
213 Ma lo sviluppatore originario dovrebbe continuare ad assumersi la
226 del kernel: Linus Torvalds. Ma, per esempio, di tutte le 9500 patch
245 del kernel, utilizzando abitualmente (ma certamente non sempre) git.
257 È chiaro che, qualche volta, guardi più attentamente. Ma, come regola
279 ma solleva anche un interessante quesito: se qualcuno volesse vedere tutte le
288 d'interesse, ma questo sarebbe un lavoro enorme e fallace.
[all …]
/linux/drivers/iio/dac/
H A Dad5758.c129 * 1000: 0 mA to 20 mA current range
130 * 1001: 0 mA to 24 mA current range
131 * 1010: 4 mA to 20 mA current range
132 * 1011: ±20 mA current range
133 * 1100: ±24 mA current range
134 * 1101: -1 mA to +22 mA current range
178 4, 12, 64, 120, 256, 500, 1820, 2048

123