From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Jani Nikula <jani.nikula@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Intel-gfx] [PATCH 0/1] add support for enum module parameters
Date: Fri, 22 Apr 2022 13:44:05 -0700 [thread overview]
Message-ID: <20220422134405.7a519a0f@kernel.org> (raw)
In-Reply-To: <87sfq8qqus.fsf@tynnyri.adurom.net>
On Wed, 20 Apr 2022 08:13:47 +0300 Kalle Valo wrote:
> Wireless drivers would also desperately need to pass device specific
> parameters at (or before) probe time. And not only debug parameters but
> also configuration parameters, for example firmware memory allocations
> schemes (optimise for features vs number of clients etc) and whatnot.
>
> Any ideas how to implement that? Is there any prior work for anything
> like this? This is pretty hard limiting usability of upstream wireless
> drivers and I really want to find a proper solution.
In netdev we have devlink which is used for all sort of device
configuration. devlink-resource sounds like what you need,
but it'd have to be extended to support configuration which requires
reload/re-probe. Currently only devlink-params support that but params
were a mistake so don't use that.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/1] add support for enum module parameters
Date: Fri, 22 Apr 2022 13:44:05 -0700 [thread overview]
Message-ID: <20220422134405.7a519a0f@kernel.org> (raw)
In-Reply-To: <87sfq8qqus.fsf@tynnyri.adurom.net>
On Wed, 20 Apr 2022 08:13:47 +0300 Kalle Valo wrote:
> Wireless drivers would also desperately need to pass device specific
> parameters at (or before) probe time. And not only debug parameters but
> also configuration parameters, for example firmware memory allocations
> schemes (optimise for features vs number of clients etc) and whatnot.
>
> Any ideas how to implement that? Is there any prior work for anything
> like this? This is pretty hard limiting usability of upstream wireless
> drivers and I really want to find a proper solution.
In netdev we have devlink which is used for all sort of device
configuration. devlink-resource sounds like what you need,
but it'd have to be extended to support configuration which requires
reload/re-probe. Currently only devlink-params support that but params
were a mistake so don't use that.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Jani Nikula <jani.nikula@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/1] add support for enum module parameters
Date: Fri, 22 Apr 2022 13:44:05 -0700 [thread overview]
Message-ID: <20220422134405.7a519a0f@kernel.org> (raw)
In-Reply-To: <87sfq8qqus.fsf@tynnyri.adurom.net>
On Wed, 20 Apr 2022 08:13:47 +0300 Kalle Valo wrote:
> Wireless drivers would also desperately need to pass device specific
> parameters at (or before) probe time. And not only debug parameters but
> also configuration parameters, for example firmware memory allocations
> schemes (optimise for features vs number of clients etc) and whatnot.
>
> Any ideas how to implement that? Is there any prior work for anything
> like this? This is pretty hard limiting usability of upstream wireless
> drivers and I really want to find a proper solution.
In netdev we have devlink which is used for all sort of device
configuration. devlink-resource sounds like what you need,
but it'd have to be extended to support configuration which requires
reload/re-probe. Currently only devlink-params support that but params
were a mistake so don't use that.
next prev parent reply other threads:[~2022-04-25 13:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 12:30 [Intel-gfx] [PATCH 0/1] add support for enum module parameters Jani Nikula
2022-04-14 12:30 ` Jani Nikula
2022-04-14 12:30 ` Jani Nikula
2022-04-14 12:30 ` [Intel-gfx] [PATCH 1/1] module: add enum module parameter type to map names to values Jani Nikula
2022-04-14 12:30 ` Jani Nikula
2022-04-14 12:30 ` Jani Nikula
2022-04-14 13:19 ` [Intel-gfx] [PATCH 0/1] add support for enum module parameters Greg Kroah-Hartman
2022-04-14 13:19 ` Greg Kroah-Hartman
2022-04-14 13:19 ` Greg Kroah-Hartman
2022-04-14 14:22 ` [Intel-gfx] " Jani Nikula
2022-04-14 14:22 ` Jani Nikula
2022-04-14 14:22 ` Jani Nikula
2022-04-14 14:29 ` [Intel-gfx] " Greg Kroah-Hartman
2022-04-14 14:29 ` Greg Kroah-Hartman
2022-04-14 14:29 ` Greg Kroah-Hartman
2022-04-20 5:13 ` [Intel-gfx] " Kalle Valo
2022-04-20 5:13 ` Kalle Valo
2022-04-20 5:13 ` Kalle Valo
2022-04-20 6:38 ` [Intel-gfx] " Greg Kroah-Hartman
2022-04-20 6:38 ` Greg Kroah-Hartman
2022-04-20 6:38 ` Greg Kroah-Hartman
2022-04-20 15:35 ` [Intel-gfx] " Ben Greear
2022-04-20 15:35 ` Ben Greear
2022-04-20 15:35 ` Ben Greear
2022-04-22 20:44 ` Jakub Kicinski [this message]
2022-04-22 20:44 ` Jakub Kicinski
2022-04-22 20:44 ` Jakub Kicinski
2022-04-14 13:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-04-14 13:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-04-14 14:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-14 16:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=20220422134405.7a519a0f@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.