[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025051433-fade-flirt-d3e0@gregkh>
Date: Wed, 14 May 2025 14:35:01 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Raag Jadav <raag.jadav@...el.com>
Cc: david.m.ertman@...el.com, ira.weiny@...el.com, lee@...nel.org,
andriy.shevchenko@...ux.intel.com, mika.westerberg@...ux.intel.com,
heikki.krogerus@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 1/2] driver core: auxiliary bus: Introduce auxiliary
device resource management
On Wed, May 14, 2025 at 05:54:31PM +0530, Raag Jadav wrote:
> With more and more drivers adopting to auxiliary bus infrastructure comes
> the need for managing resources at auxiliary device level. This is useful
> for cases where parent device shares variable number and type of resources
> with auxiliary child device but doesn't require any active involvement in
> managing them.
>
> This reduces potential duplication of resource APIs that may be required by
> parent device driver. With this in place parent driver will be responsible
> for filling up respective resources and its count in auxiliary device
> structure before registering it, so that the leaf drivers can utilize in
> their probe function. Lifecycle of these resources will be as long as the
> auxiliary device exists.
>
> Signed-off-by: Raag Jadav <raag.jadav@...el.com>
> ---
> drivers/base/auxiliary.c | 145 ++++++++++++++++++++++++++++++++++
> include/linux/auxiliary_bus.h | 18 +++++
> 2 files changed, 163 insertions(+)
Sorry, but again, you are not following the required rules for Intel
kernel submissions for this subsystem. Please work with the Intel
kernel team to fix this up before you resend.
greg k-h
Powered by blists - more mailing lists