[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6U0qdithzESpWXcYv2JX0hfg_wieJBkt2LEiCAtBJQQgA@mail.gmail.com>
Date: Wed, 11 Jan 2017 11:25:15 -0600
From: "Luis R. Rodriguez" <mcgrof@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Ming Lei <ming.lei@...onical.com>,
Daniel Wagner <daniel.wagner@...-carit.de>,
Tom Gundersen <teg@...m.no>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Rafał Miłecki <zajec5@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vikram Mulukutla <markivx@...eaurora.org>,
Stephen Boyd <stephen.boyd@...aro.org>,
Mark Brown <broonie@...nel.org>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Takashi Iwai <tiwai@...e.de>,
Johannes Berg <johannes@...solutions.net>,
Christian Lamparter <chunkeey@...glemail.com>,
Hauke Mehrtens <hauke@...ke-m.de>,
Josh Boyer <jwboyer@...oraproject.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Jiri Slaby <jslaby@...e.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Fengguang Wu <fengguang.wu@...el.com>,
Richard Purdie <rpurdie@...ys.net>,
Jacek Anaszewski <j.anaszewski@...sung.com>,
Abhay Salunke <Abhay_Salunke@...l.com>,
Julia Lawall <Julia.Lawall@...6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
David Howells <dhowells@...hat.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Arend Van Spriel <arend.vanspriel@...adcom.com>,
Kalle Valo <kvalo@...eaurora.org>, linux-leds@...r.kernel.org
Subject: Re: [PATCH v2 4/5] firmware: add SmPL report for custom fallback mechanism
On Wed, Jan 11, 2017 at 9:49 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Wed, Jan 11, 2017 at 03:02:22PM +0100, Luis R. Rodriguez wrote:
>> On Wed, Jan 11, 2017 at 09:32:26AM +0100, Greg KH wrote:
>> > On Fri, Dec 16, 2016 at 03:10:37AM -0800, 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.
>> >
>> > Well, the biggest reason is that some distros still rely on this. I've
>> > seen new products being made that rely on it,
>>
>> Let's be a bit more precise: upstream there are only two driver relying on this
>> and I've learned about the non-upstream uses which folks have been calling for
>> ensuring this functionality is kept for: a) non-upstream mobile 802.11 drivers or
>> upstream 802.11 drivers with slight out-of-tree customizations with a requirements to
>> get calibration data using custom mechanisms b) remote-proc users with huge firmware
>> requirements for which initramfs is not well suited for.
>
> That b) is a lot of devices, I know of a few million phones in the wild
> right now that rely on it. And millions is a pretty big number :)
>
> Anyway, thanks for addressing my concerns, I'm guessing you will respin
> these remaining patches and resend them as I think there were still some
> comments on them? I took the first 3 here.
Yeah sure, I will address these comments.
> Is the "drvdata" code ready in your opinion to be merged / reviewed yet?
drvdata stuff is ready as can be but after the sysdata/drvdata rename
change I failed to change one of the p54 files, I also forgot to Cc
Boris on the microcode conversion so I can just respin the drvdata
series again as a separate series right after I address the concerns
for this series.
Luis
Powered by blists - more mailing lists