[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200706135717.GB919533@lunn.ch>
Date: Mon, 6 Jul 2020 15:57:17 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Diana Craciun <diana.craciun@....com>
Cc: linux-kernel@...r.kernel.org, laurentiu.tudor@....com,
gregkh@...uxfoundation.org, stuyoder@...il.com, leoyang.li@....com,
bharatb.linux@...il.com, Diana Craciun <diana.craciun@....nxp.com>,
Bharat Bhushan <Bharat.Bhushan@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 03/13] bus/fsl-mc: add support for 'driver_override'
in the mc-bus
Hi Diana
On Mon, Jul 06, 2020 at 03:42:33PM +0300, Diana Craciun wrote:
> From: Bharat Bhushan <Bharat.Bhushan@....com>
>
> This patch is required for vfio-fsl-mc meta driver to successfully bind
> layerscape container devices for device passthrough. This patch adds
> a mechanism to allow a layerscape device to specify a driver rather than
> a layerscape driver provide a device match.
>
> Example to allow a device (dprc.1) to specifically bind
> with driver (vfio-fsl-mc):-
> - echo vfio-fsl-mc > /sys/bus/fsl-mc/devices/dprc.1/driver_override
> - echo dprc.1 > /sys/bus/fsl-mc/drivers/fsl_mc_dprc/unbind
> - echo dprc.1 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind
Something i asked before, why is this buried in a driver, when it
could be put in the driver core. This is not the only driver doing
this, so it does make sense to share the code and bugs.
Andrew
Powered by blists - more mailing lists