On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahas...@baylibre.com wrote:
> From: Axel Haslam
>
> Some regulator supplies have an over-current pin that is
> activated when the hw detects an over current condition.
> When this happens, the hardware enters a current limited
>
On Tue, Oct 25, 2016 at 4:57 PM, Axel Haslam wrote:
> On Tue, Oct 25, 2016 at 4:33 PM, Mark Brown wrote:
>> On Tue, Oct 25, 2016 at 02:55:48PM +0200, Axel Haslam wrote:
>>
>>> To be able to use regulator to handle the overcurrent pin, i need to be able
On Tue, Oct 25, 2016 at 4:33 PM, Mark Brown wrote:
> On Tue, Oct 25, 2016 at 02:55:48PM +0200, Axel Haslam wrote:
>
>> To be able to use regulator to handle the overcurrent pin, i need to be able
>> to somehow retrieve the over current pin state from the regulator driver.
>
>
On Tue, Oct 25, 2016 at 02:55:48PM +0200, Axel Haslam wrote:
> To be able to use regulator to handle the overcurrent pin, i need to be able
> to somehow retrieve the over current pin state from the regulator driver.
What makes you say that, none of the existing users need this?
> As i was
Hi Mark,
On Mon, Oct 24, 2016 at 8:19 PM, Mark Brown wrote:
> On Mon, Oct 24, 2016 at 08:11:40PM +0200, Axel Haslam wrote:
>> On Mon, Oct 24, 2016 at 7:53 PM, Mark Brown wrote:
>
>> > does it make sense to report this as a mode, we don't report other
On Mon, Oct 24, 2016 at 08:11:40PM +0200, Axel Haslam wrote:
> On Mon, Oct 24, 2016 at 7:53 PM, Mark Brown wrote:
> > does it make sense to report this as a mode, we don't report other error
> > conditions as modes but instead use REGULATOR_STATUS_ with the
> > get_status()
On Mon, Oct 24, 2016 at 7:53 PM, Mark Brown wrote:
> On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahas...@baylibre.com wrote:
>
>> + if (ret) {
>> + pr_err("Failed to request irq: %d\n", ret);
>
> dev_err()
>
>> +++
Hi Mark,
On Mon, Oct 24, 2016 at 7:43 PM, Mark Brown wrote:
> On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahas...@baylibre.com wrote:
>> From: Axel Haslam
>>
>> Some regulator supplies have an over-current pin that is
>> activated when the hw detects an
On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahas...@baylibre.com wrote:
> + if (ret) {
> + pr_err("Failed to request irq: %d\n", ret);
dev_err()
> +++ b/include/linux/regulator/consumer.h
> @@ -74,6 +74,10 @@
> * the most noisy and may not be able to
On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahas...@baylibre.com wrote:
> From: Axel Haslam
>
> Some regulator supplies have an over-current pin that is
> activated when the hw detects an over current condition.
> When this happens, the hardware enters a current limited
>
From: Axel Haslam
Some regulator supplies have an over-current pin that is
activated when the hw detects an over current condition.
When this happens, the hardware enters a current limited
mode.
Extend the fixed regulator driver with the ability
to handle irq's from the
11 matches
Mail list logo