Re: [PATCH] driver core: Make probe_type of driver accessible via sysfs

From: Wenchao Hao <haowenchao@huawei.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	<linux-kernel@vger.kernel.org>, <linfeilong@huawei.com>,
	Wu Bo <wubo40@huawei.com>,
	Zhiqiang Liu <liuzhiqiang26@huawei.com>
Subject: Re: [PATCH] driver core: Make probe_type of driver accessible via sysfs
Date: Thu, 8 Jul 2021 20:49:31 +0800	[thread overview]
Message-ID: <d2a5f7f3-f68f-9420-b7ee-43102adf514f@huawei.com> (raw)
In-Reply-To: <YObvYiPxQC7lk3NT@kroah.com>

In some scenarios, you need to know whether the probe() callback in struct
driver which triggered by device_add() or driver_register() is called
synchronous or not, and modify this mode according to user requirements.

While kernel now does not open an interface for users to query or
modify, so I add this interface.

I ignored updates to ABI document due to no previous experience with ABI 
change,
and I will bring updates to the ABI in next submission.

On 2021/7/8 20:28, Greg Kroah-Hartman wrote:
> On Thu, Jul 08, 2021 at 08:20:10PM +0800, Wenchao Hao wrote:
>> Like drivers_autoprobe of bus, make probe_type of driver
>> accessible via sysfs, so we can get and set a driver's probe_type
>> happily.
> Why is this needed?  Who will use it?  And where is the
> Documentation/ABI/ file update for this new sysfs file which is required
> for all sysfs files?
>
> thanks,
>
> greg k-h
> .