public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "J. German Rivera" <German.Rivera@freescale.com>
Cc: arnd@arndb.de, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, stuart.yoder@freescale.com,
	bhupesh.sharma@freescale.com, agraf@suse.de,
	bhamciu1@freescale.com,
	Bharat Bhushan <bharat.bhushan@freescale.com>,
	nir.erez@freescale.com, itai.katz@freescale.com,
	scottwood@freescale.com, R89243@freescale.com,
	richard.schmitt@freescale.com
Subject: Re: [PATCH v2 2/7] staging: fsl_-mc: add device binding path 'driver_override'
Date: Sun, 10 May 2015 15:16:09 +0200	[thread overview]
Message-ID: <20150510131609.GB4608@kroah.com> (raw)
In-Reply-To: <1430947708-10521-3-git-send-email-German.Rivera@freescale.com>

On Wed, May 06, 2015 at 04:28:23PM -0500, J. German Rivera wrote:
> From: Bharat Bhushan <bharat.bhushan@freescale.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.
> 
> This patch is based on following proposed patches for PCI and platform devices
> - https://lkml.org/lkml/2014/4/8/571  :- For Platform devices
> - http://lists-archives.com/linux-kernel/28030441-pci-introduce-new-device-binding-path-using-pci_dev-driver_override.html  :- For PCI devices
> 
> 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
> 
> Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
> Reviewed-by: Stuart Yoder <stuart.yoder@freescale.com>
> Tested-by: Stuart Yoder <stuart.yoder@freescale.com>
> ---
> Changes in v2:
> none
> 
>  drivers/staging/fsl-mc/bus/mc-bus.c | 67 +++++++++++++++++++++++++++++++++++++
>  drivers/staging/fsl-mc/include/mc.h |  2 ++
>  2 files changed, 69 insertions(+)
> 
> diff --git a/drivers/staging/fsl-mc/bus/mc-bus.c b/drivers/staging/fsl-mc/bus/mc-bus.c
> index d51120a..0e9cba8 100644
> --- a/drivers/staging/fsl-mc/bus/mc-bus.c
> +++ b/drivers/staging/fsl-mc/bus/mc-bus.c
> @@ -58,6 +58,12 @@ static int fsl_mc_bus_match(struct device *dev, struct device_driver *drv)
>  	if (WARN_ON(!fsl_mc_bus_type.dev_root))
>  		goto out;
> 
> +	/* When driver_override is set, only bind to the matching driver */
> +	if (mc_dev->driver_override) {
> +		found = !strcmp(mc_dev->driver_override, mc_drv->driver.name);
> +		goto out;
> +	}
> +
>  	if (!mc_drv->match_id_table)
>  		goto out;
> 
> @@ -116,10 +122,69 @@ static int fsl_mc_bus_uevent(struct device *dev, struct kobj_uevent_env *env)
>  	return 0;
>  }
> 
> +static ssize_t driver_override_store(struct device *dev,
> +				     struct device_attribute *attr,
> +				     const char *buf, size_t count)
> +{
> +	struct fsl_mc_device *mc_dev = to_fsl_mc_device(dev);
> +	const char *driver_override, *old = mc_dev->driver_override;
> +	char *cp;
> +
> +	if (WARN_ON(dev->bus != &fsl_mc_bus_type))
> +		return -EINVAL;
> +
> +	if (count > PATH_MAX)
> +		return -EINVAL;
> +
> +	driver_override = kstrndup(buf, count, GFP_KERNEL);
> +	if (!driver_override)
> +		return -ENOMEM;
> +
> +	cp = strchr(driver_override, '\n');
> +	if (cp)
> +		*cp = '\0';
> +
> +	if (strlen(driver_override)) {
> +		mc_dev->driver_override = driver_override;
> +	} else {
> +		kfree(driver_override);
> +		mc_dev->driver_override = NULL;
> +	}
> +
> +	kfree(old);
> +
> +	return count;
> +}
> +
> +static ssize_t driver_override_show(struct device *dev,
> +				    struct device_attribute *attr, char *buf)
> +{
> +	struct fsl_mc_device *mc_dev = to_fsl_mc_device(dev);
> +
> +	return sprintf(buf, "%s\n", mc_dev->driver_override);
> +}
> +
> +static DEVICE_ATTR_RW(driver_override);

Documenation for this new sysfs attribute?

> +
> +static struct attribute *fsl_mc_dev_attrs[] = {
> +	&dev_attr_driver_override.attr,
> +	NULL,
> +};
> +
> +static const struct attribute_group fsl_mc_dev_group = {
> +	.attrs = fsl_mc_dev_attrs,
> +};
> +
> +static const struct attribute_group *fsl_mc_dev_groups[] = {
> +	&fsl_mc_dev_group,
> +	NULL,
> +};

ATTRIBUTE_GROUP()?


  reply	other threads:[~2015-05-10 21:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 21:28 [PATCH v2 0/7] staging: fsl-mc: New functionality to the MC bus driver J. German Rivera
2015-05-06 21:28 ` [PATCH v2 1/7] staging: fsl-mc: MC bus IRQ support J. German Rivera
2015-05-07 13:03   ` Dan Carpenter
2015-05-07 14:51     ` German Rivera
2015-05-07 20:01       ` Dan Carpenter
2015-05-10 13:14         ` Greg KH
2015-05-07 13:58   ` Dan Carpenter
2015-05-06 21:28 ` [PATCH v2 2/7] staging: fsl_-mc: add device binding path 'driver_override' J. German Rivera
2015-05-10 13:16   ` Greg KH [this message]
2015-05-06 21:28 ` [PATCH v2 3/7] staging: fsl-mc: Propagate driver_override for a child DPRC's children J. German Rivera
2015-05-06 21:28 ` [PATCH v2 4/7] staging: fsl-mc: Upgraded MC bus driver to match MC fw 7.0.0 J. German Rivera
2015-05-08  7:22   ` Dan Carpenter
2015-05-06 21:28 ` [PATCH v2 5/7] staging: fsl-mc: Allow the MC bus driver to run without GIC support J. German Rivera
2015-05-06 21:28 ` [PATCH v2 6/7] staging: fsl-mc: Add locking to serialize mc_send_command() calls J. German Rivera
2015-05-06 21:28 ` [PATCH v2 7/7] staging: fsl-mc: Use DPMCP IRQ and completion var to wait for MC J. German Rivera

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150510131609.GB4608@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=German.Rivera@freescale.com \
    --cc=R89243@freescale.com \
    --cc=agraf@suse.de \
    --cc=arnd@arndb.de \
    --cc=bhamciu1@freescale.com \
    --cc=bharat.bhushan@freescale.com \
    --cc=bhupesh.sharma@freescale.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=itai.katz@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.erez@freescale.com \
    --cc=richard.schmitt@freescale.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox