From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932618AbbJPTfS (ORCPT <rfc822;w@1wt.eu>);
	Fri, 16 Oct 2015 15:35:18 -0400
Received: from mx2.suse.de ([195.135.220.15]:45638 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753550AbbJPTfQ (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 16 Oct 2015 15:35:16 -0400
Date: Fri, 16 Oct 2015 21:35:12 +0200
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Ming Lei <ming.lei@canonical.com>, Takashi Iwai <tiwai@suse.de>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Liam Girdwood <liam.r.girdwood@linux.intel.com>,
        "Jie, Yang" <yang.jie@intel.com>,
        "joonas.lahtinen@linux.intel.com" <joonas.lahtinen@linux.intel.com>,
        Al Viro <viro@zeniv.linux.org.uk>, Kay Sievers <kay@vrfy.org>,
        David Woodhouse <dwmw2@infradead.org>,
        lkml <linux-kernel@vger.kernel.org>,
        yalin wang <yalin.wang2010@gmail.com>, Tom Gundersen <teg@jklm.no>,
        Johannes Berg <johannes@sipsolutions.net>,
        Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: Problems loading firmware using built-in drivers with kernels
 that use initramfs.
Message-ID: <20151016193512.GC9528@wotan.suse.de>
References: <55E6E70F.80907@broadcom.com>
 <55E6E7FD.8030401@broadcom.com>
 <20150902185842.GC8051@wotan.suse.de>
 <55E76418.7070006@broadcom.com>
 <CAKdAkRSWghMptgD3hfr6VJBrAyzLw+p842zSNovHKSqJiGOP1w@mail.gmail.com>
 <20150902232249.GK8051@wotan.suse.de>
 <CAKdAkRSbt4_z3HBHYhzSTLNxnfQD59-X6asXf5nsgxy8tyeW9A@mail.gmail.com>
 <CAB=NE6UBRa0K7=PomJzKxsoj4GzAqkYrkp=O+UfVvu2fwM25pA@mail.gmail.com>
 <55E88206.5050106@broadcom.com>
 <CAKdAkRQ9ibgW60t8xNy7_vo3BY0979xfVGaQu8u9LGaWgY+=AQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKdAkRQ9ibgW60t8xNy7_vo3BY0979xfVGaQu8u9LGaWgY+=AQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Sep 03, 2015 at 10:33:51AM -0700, Dmitry Torokhov wrote:
> On Thu, Sep 3, 2015 at 10:23 AM, Arend van Spriel <arend@broadcom.com> wrote:
> > On 09/03/2015 01:46 AM, Luis R. Rodriguez wrote:
> >>
> >> On Wed, Sep 2, 2015 at 4:29 PM, Dmitry Torokhov
> >> <dmitry.torokhov@gmail.com> wrote:
> >>>
> >>> On Wed, Sep 2, 2015 at 4:22 PM, Luis R. Rodriguez <mcgrof@suse.com>
> >>> wrote:
> >>>> IMHO its just as hacky as using -EPROBE_DEFER too, but its at least
> >>>> preemptively hacky. Sadly I can't think of clear and clever way for the
> >>>> kernel
> >>>> to know when firmware will be ready either...  Would userspace know?
> >>>> Should the
> >>>> kernel learn this from userspace ?
> >>>
> >>>
> >>> Yes. Given only userspace knows when firmware is available (I could
> >>> have it on a separate device and mount it at some time). So maybe
> >>> userpsace should simply try and scan busses for unbound devices and
> >>> tell them to re-probe when it decides that firmware is finally
> >>> available.
> >>
> >>
> >> OK, the folks wanting this mechanism can implement it then. Short of
> >> that we only have hacks.
> >
> >
> > So what does "userspace knows when firmware is available" mean here. The
> > specific firmware file the driver wants or the collection of firmware files
> > which may or may not have the specific firmware file the driver wants. I
> > assume the latter and re-probe will fail as expected.
> 
> Right, the latter.

Arend, curious are you working on this? Me and Julia did some hunting and
have found quite a bit of users that could use this. I'll provide results
in another thread but figured I'd follow up to see if anyone is working
to address this. Otherwise we just have hacks for now.

 Luis