From: Kim Phillips <kim.phillips@freescale.com>
To: Antonios Motakis <a.motakis@virtualopensystems.com>
Cc: Russell King <linux@arm.linux.org.uk>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
kvmarm@lists.cs.columbia.edu, iommu@lists.linux-foundation.org,
alex.williamson@redhat.com, tech@virtualopensystems.com,
christoffer.dall@linaro.org, eric.auger@linaro.org,
marc.zyngier@arm.com
Subject: Re: [PATCH] driver core: amba: add device binding path 'driver_override'
Date: Mon, 13 Oct 2014 08:23:24 -0500 [thread overview]
Message-ID: <20141013082324.362423be23ad44dc391ccd65@freescale.com> (raw)
In-Reply-To: <1413205672-6236-1-git-send-email-a.motakis@virtualopensystems.com>
On Mon, 13 Oct 2014 15:07:34 +0200
Antonios Motakis <a.motakis@virtualopensystems.com> wrote:
> As already demonstrated with PCI [1] and the platform bus [2], a
> driver_override property in sysfs can be used to bypass the id matching
> of a device to a AMBA driver. This can be used by VFIO to bind to any AMBA
> device requested by the user.
>
> [1] http://lists-archives.com/linux-kernel/28030441-pci-introduce-new-device-binding-path-using-pci_dev-driver_override.html
> [2] https://www.redhat.com/archives/libvir-list/2014-April/msg00382.html
>
> Signed-off-by: Antonios Motakis <a.motakis@virtualopensystems.com>
> ---
Reviewed-by: Kim Phillips <kim.phillips@freescale.com>
Kim
prev parent reply other threads:[~2014-10-13 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 13:07 [PATCH] driver core: amba: add device binding path 'driver_override' Antonios Motakis
2014-10-13 13:23 ` Kim Phillips [this message]
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=20141013082324.362423be23ad44dc391ccd65@freescale.com \
--to=kim.phillips@freescale.com \
--cc=a.motakis@virtualopensystems.com \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=tech@virtualopensystems.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;
as well as URLs for NNTP newsgroup(s).