Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1483513
| From | NeilBrown <neilb@suse.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation |
| Date | 2016-09-14 20:00 +0200 |
| Message-ID | <shmDw-3Sa-11@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <sgBlf-548-9@gated-at.bofh.it> <sgQWZ-7Cf-1@gated-at.bofh.it> <shgoq-ao-27@gated-at.bofh.it> <shjcB-1Ui-3@gated-at.bofh.it> <shjPk-27U-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Wed, Sep 14 2016, Mark Brown wrote: > TI do a lot of the more software managed chargers (which I suspect are > the main thing Felipe will have looked at) if that's what you're > referring to here? The device is implementing pretty much the algorithm > you're describing in that e-mail so I'm a bit confused as to what you're > saying here. Ah.... my mistake, sorry. When earlier you said: > It's a > current limiter intended to sit in line with the USB power lines to > ensure the system doesn't go over the maximum current draw (and also > integrates with the power source selection logic the chip has to pick > the best available power source for the system). I assumed that all it did was limit the current to number given. If it also limits the current to ensure that voltage doesn't drop unduly, then I agree with your assertion that it just needs to be told the upper limit. I hope you'll agree that other drivers might need to know the lower limit, so reporting both to all drivers is sensible. Thanks, NeilBrown
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation NeilBrown <neilb@suse.com> - 2016-09-10 00:00 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Mark Brown <broonie@kernel.org> - 2016-09-12 14:30 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation NeilBrown <neilb@suse.com> - 2016-09-12 15:30 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Mark Brown <broonie@kernel.org> - 2016-09-12 17:30 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation NeilBrown <neilb@suse.com> - 2016-09-13 10:10 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Mark Brown <broonie@kernel.org> - 2016-09-14 13:20 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation NeilBrown <neilb@suse.com> - 2016-09-14 16:20 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Mark Brown <broonie@kernel.org> - 2016-09-14 17:00 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation NeilBrown <neilb@suse.com> - 2016-09-14 20:00 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Mark Brown <broonie@kernel.org> - 2016-09-14 20:10 +0200
Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Pavel Machek <pavel@ucw.cz> - 2016-09-15 12:40 +0200
csiph-web