On 2018-05-08 22:49, Bjorn Andersson wrote:
On Tue 08 May 05:26 PDT 2018, kgu...@codeaurora.org wrote:
On 2018-05-07 22:51, Bjorn Andersson wrote:
> On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote:
[..]
> > @@ -220,7 +255,12 @@ static int wled_module_enable(struct wled
> > *wled, int val)
>
On 2018-05-09 10:36, kgu...@codeaurora.org wrote:
On 2018-05-08 22:49, Bjorn Andersson wrote:
On Tue 08 May 05:26 PDT 2018, kgu...@codeaurora.org wrote:
On 2018-05-07 22:51, Bjorn Andersson wrote:
> On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote:
[..]
> > @@ -220,7 +255,12 @@ static int
On Tue 08 May 05:26 PDT 2018, kgu...@codeaurora.org wrote:
> On 2018-05-07 22:51, Bjorn Andersson wrote:
> > On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote:
[..]
> > > @@ -220,7 +255,12 @@ static int wled_module_enable(struct wled
> > > *wled, int val)
> > >
On 2018-05-07 22:51, Bjorn Andersson wrote:
On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote:
WLED peripheral has over voltage protection(OVP) circuitry and the OVP
fault is notified through an interrupt. Though this fault condition
rising
is due to an incorrect hardware configuration is
On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote:
> WLED peripheral has over voltage protection(OVP) circuitry and the OVP
> fault is notified through an interrupt. Though this fault condition rising
> is due to an incorrect hardware configuration is mitigated in the hardware,
> it still needs to
WLED peripheral has over voltage protection(OVP) circuitry and the OVP
fault is notified through an interrupt. Though this fault condition rising
is due to an incorrect hardware configuration is mitigated in the hardware,
it still needs to be detected and handled. Add support for it.
When WLED
