From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] VFIO: platform: AMD xgbe reset module
Date: Thu, 15 Oct 2015 16:28:17 +0200 [thread overview]
Message-ID: <9585756.nfBEboTrrV@wuerfel> (raw)
In-Reply-To: <561FB63E.4070404@linaro.org>
On Thursday 15 October 2015 16:20:46 Eric Auger wrote:
> On 10/15/2015 02:12 PM, Christoffer Dall wrote:
> > On Thu, Oct 15, 2015 at 01:21:55PM +0200, Arnd Bergmann wrote:
> >> On Thursday 15 October 2015 10:08:02 Eric Auger wrote:
> >>> On 10/14/2015 05:38 PM, Arnd Bergmann wrote:
> >>>> On Wednesday 14 October 2015 15:33:12 Eric Auger wrote:
> >> A possible solution could be something inside the xgbe driver like
> >>
> >>
> >> static void xgbe_init_module(void)
> >> {
> >> int ret = 0;
> >>
> >> if (IS_ENABLED(CONFIG_AMD_XGBE_ETHERNET)
> >> ret = platform_driver_register(&xgbe_driver);
> >> if (ret)
> >> return ret;
> >>
> >> if (IS_ENABLED(CONFIG_VFIO_PLATFORM))
> >> ret = vfio_platform_register_reset(&xgbe_of_match, xgbe_platform_reset);
> >>
> >> return ret;
> >> }
> >>
> >> This way you have exactly one driver module that gets loaded for the
> >> device and you can use it either with the platform_driver or through
> >> vfio.
> If I understand it correctly you still need 2 loaded modules (VFIO
> driver & XGBE driver which implements the reset function) or am I
> missing something?
That is correct, yes.
> I had a similar mechanism of registration in my PATCH v1 but I did the
> registration from the reset module itself instead of in the native
> driver, as you suggest here.
Right. The main difference is that you don't have two modules fighting
over the same device with the approach here.
Arnd
prev parent reply other threads:[~2015-10-15 14:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 15:33 [PATCH] VFIO: platform: AMD xgbe reset module Eric Auger
2015-10-14 15:38 ` Arnd Bergmann
2015-10-15 8:08 ` Eric Auger
2015-10-15 11:21 ` Arnd Bergmann
2015-10-15 12:12 ` Christoffer Dall
2015-10-15 13:59 ` Arnd Bergmann
2015-10-15 14:46 ` Eric Auger
2015-10-15 14:55 ` Arnd Bergmann
2015-10-15 15:03 ` Christoffer Dall
2015-10-15 15:49 ` Arnd Bergmann
2015-10-15 16:35 ` Christoffer Dall
2015-10-15 16:53 ` Alex Williamson
2015-10-15 19:42 ` Christoffer Dall
2015-10-15 20:26 ` Alex Williamson
2015-10-16 13:06 ` Eric Auger
2015-10-16 13:26 ` Arnd Bergmann
2015-10-16 13:56 ` Eric Auger
2015-10-15 14:20 ` Eric Auger
2015-10-15 14:28 ` Arnd Bergmann [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=9585756.nfBEboTrrV@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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