On Fri, Dec 16, 2016 at 10:29:52AM +0100, Luis R. Rodriguez wrote:
> On Wed, Dec 14, 2016 at 10:48:37AM +0900, Milo Kim wrote:
> > Hi Jacek,
> >
> > On 12/13/2016 06:44 PM, Jacek Anaszewski wrote:
> > >
> > > Could you please verify if leds-lp55xx-common.c driver
> > > really needs a custom firmw
On Wed, Dec 14, 2016 at 10:48:37AM +0900, Milo Kim wrote:
> Hi Jacek,
>
> On 12/13/2016 06:44 PM, Jacek Anaszewski wrote:
> >
> > Could you please verify if leds-lp55xx-common.c driver
> > really needs a custom firmware loading fallback mechanism?
>
> Thanks for sharing this. The lp55xx-common u
Hi Jacek,
On 12/13/2016 06:44 PM, Jacek Anaszewski wrote:
Could you please verify if leds-lp55xx-common.c driver
really needs a custom firmware loading fallback mechanism?
Thanks for sharing this. The lp55xx-common uses this mechanism to load
and run LED effect manually, so this could be a m
Hi Milo,
Could you please verify if leds-lp55xx-common.c driver
really needs a custom firmware loading fallback mechanism?
See [0] to gain some background knowledge, especially patch 3/5 seems
to provide a big amount of information.
[0] https://lkml.org/lkml/2016/12/12/717
Thanks,
Jacek Anaszew
On Mon, 12 Dec 2016, Luis R. Rodriguez wrote:
> Even though most distributions today disable the fallback mechanism
> by default we've determined that we cannot remove them from the kernel.
> This is not well understood so document the reason and logic behind that.
>
> Recent discussions suggest
5 matches
Mail list logo
