From: Dave Jiang <dave.jiang@intel.com>
To: Fenghua Yu <fenghua.yu@intel.com>, Vinod Koul <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michael Prinke <michael.prinke@intel.com>
Subject: Re: [PATCH] dmaengine: idxd: Register dsa_bus_type before registering idxd sub-drivers
Date: Tue, 26 Sep 2023 10:23:04 -0700 [thread overview]
Message-ID: <983b5c76-f611-ffa3-683a-f754efab9d4c@intel.com> (raw)
In-Reply-To: <20230924162232.1409454-1-fenghua.yu@intel.com>
On 9/24/23 09:22, Fenghua Yu wrote:
> idxd sub-drivers belong to bus dsa_bus_type. Thus, dsa_bus_type must be
> registered in dsa bus init before idxd drivers can be registered.
>
> But the order is wrong when both idxd and idxd_bus are builtin drivers.
> In this case, idxd driver is compiled and linked before idxd_bus driver.
> Since the initcall order is determined by the link order, idxd sub-drivers
> are registered in idxd initcall before dsa_bus_type is registered
> in idxd_bus initcall. idxd initcall fails:
>
> [ 21.562803] calling idxd_init_module+0x0/0x110 @ 1
> [ 21.570761] Driver 'idxd' was unable to register with bus_type 'dsa' because the bus was not initialized.
> [ 21.586475] initcall idxd_init_module+0x0/0x110 returned -22 after 15717 usecs
> [ 21.597178] calling dsa_bus_init+0x0/0x20 @ 1
>
> To fix the issue, compile and link idxd_bus driver before idxd driver
> to ensure the right registration order.
>
> Fixes: d9e5481fca74 ("dmaengine: dsa: move dsa_bus_type out of idxd driver to standalone")
> Reported-by: Michael Prinke <michael.prinke@intel.com>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/idxd/Makefile | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/idxd/Makefile b/drivers/dma/idxd/Makefile
> index dc096839ac63..c5e679070e46 100644
> --- a/drivers/dma/idxd/Makefile
> +++ b/drivers/dma/idxd/Makefile
> @@ -1,12 +1,12 @@
> ccflags-y += -DDEFAULT_SYMBOL_NAMESPACE=IDXD
>
> +obj-$(CONFIG_INTEL_IDXD_BUS) += idxd_bus.o
> +idxd_bus-y := bus.o
> +
> obj-$(CONFIG_INTEL_IDXD) += idxd.o
> idxd-y := init.o irq.o device.o sysfs.o submit.o dma.o cdev.o debugfs.o
>
> idxd-$(CONFIG_INTEL_IDXD_PERFMON) += perfmon.o
>
> -obj-$(CONFIG_INTEL_IDXD_BUS) += idxd_bus.o
> -idxd_bus-y := bus.o
> -
> obj-$(CONFIG_INTEL_IDXD_COMPAT) += idxd_compat.o
> idxd_compat-y := compat.o
next prev parent reply other threads:[~2023-09-26 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 16:22 Fenghua Yu
2023-09-26 16:27 ` Lijun Pan
2023-09-26 17:23 ` Dave Jiang [this message]
2023-09-28 11:56 ` Vinod Koul
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=983b5c76-f611-ffa3-683a-f754efab9d4c@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.prinke@intel.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®