On 1/30/25 11:05 PM, Saket Kumar Bhaskar wrote:
On powerpc, a CPU does not necessarily originate from NUMA node 0.
This contrasts with architectures like x86, where CPU 0 is not
hot-pluggable, making NUMA node 0 a consistently valid node.
This discrepancy can lead to failures when creating a
Broadcasting flags are hardcoded for each kind for protocol.
Create a redirect_flags map that allows to select the broadcasting flags
to use in the bpf_redirect_map(). The protocol ID is used as a key.
Set the old hardcoded values as default if the map isn't filled by the
BPF caller.
Ack
On powerpc, a CPU does not necessarily originate from NUMA node 0.
This contrasts with architectures like x86, where CPU 0 is not
hot-pluggable, making NUMA node 0 a consistently valid node.
This discrepancy can lead to failures when creating a map on NUMA
node 0, which is initialized by default, i
Broadcasting flags are hardcoded for each kind for protocol.
Create a redirect_flags map that allows to select the broadcasting flags
to use in the bpf_redirect_map(). The protocol ID is used as a key.
Set the old hardcoded values as default if the map isn't filled by the
BPF caller.
Ack
BUILD and this test suite on a system where REGMAP is not
> enabled by default.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] firmware: cs_dsp: FW_CS_DSP_KUNIT_TEST should not select REGMAP
commit: eb5c79828cfa72e8d
On Sat, Jan 25, 2025 at 09:02:37AM -0800, Alexei Starovoitov wrote:
> On Sat, Jan 25, 2025 at 7:25 AM Saket Kumar Bhaskar
> wrote:
> >
> > On powerpc, a CPU does not necessarily originate from NUMA node 0.
> > This contrasts with architectures like x86, where CPU 0 is not
> > hot-pluggable, makin
mware: cs_dsp: Add KUnit testing of bin file
download")
Signed-off-by: Geert Uytterhoeven
---
See also commits 70a640c0efa76674 ("regmap: REGMAP_KUNIT should not
select REGMAP") and 47ee108a113c72e ("regmap: Provide user selectable
option to enable regmap").
BTW, what&
On Sat, Jan 25, 2025 at 7:25 AM Saket Kumar Bhaskar wrote:
>
> On powerpc, a CPU does not necessarily originate from NUMA node 0.
> This contrasts with architectures like x86, where CPU 0 is not
> hot-pluggable, making NUMA node 0 a consistently valid node.
> This discrepancy can lead to failures
On powerpc, a CPU does not necessarily originate from NUMA node 0.
This contrasts with architectures like x86, where CPU 0 is not
hot-pluggable, making NUMA node 0 a consistently valid node.
This discrepancy can lead to failures when creating a map on NUMA
node 0, which is initialized by default, i
Broadcasting flags are hardcoded for each kind for protocol.
Create a redirect_flags map that allows to select the broadcasting flags
to use in the bpf_redirect_map(). The protocol ID is used as a key.
Set the old hardcoded values as default if the map isn't filled by the
BPF caller.
Signe
Broadcasting flags are hardcoded for each kind for protocol.
Create a redirect_flags map that allows to select the broadcasting flags
to use in the bpf_redirect_map(). The protocol ID is used as a key.
Set the old hardcoded values as default if the map isn't filled by the
BPF caller.
Signe
On Mon, Dec 30, 2024 at 8:45 PM Cindy Lu wrote:
>
> The vhost now uses vhost_task and workers as a child of the owner
> thread. While this aligns with containerization principles, it confuses
> some legacy userspace applications. Therefore, we are reintroducing
> support for the kthread API.
>
> I
The vhost now uses vhost_task and workers as a child of the owner
thread. While this aligns with containerization principles, it confuses
some legacy userspace applications. Therefore, we are reintroducing
support for the kthread API.
Introduce a new parameter to enable users to choose between kth
On Wed, Dec 11, 2024 at 1:52 AM Stefano Garzarella wrote:
>
> On Wed, Dec 11, 2024 at 12:41:40AM +0800, Cindy Lu wrote:
> >The vhost now uses vhost_task and workers as a child of the owner thread.
> >While this aligns with containerization principles,it confuses some legacy
>
> nit: missing space
On Wed, Dec 11, 2024 at 12:41:40AM +0800, Cindy Lu wrote:
The vhost now uses vhost_task and workers as a child of the owner thread.
While this aligns with containerization principles,it confuses some legacy
nit: missing space in "principles,it"
userspace app, Therefore, we are reintroducing k
The vhost now uses vhost_task and workers as a child of the owner thread.
While this aligns with containerization principles,it confuses some legacy
userspace app, Therefore, we are reintroducing kthread API support.
Introduce a new parameter to enable users to choose between
kthread and task mode
On Tue, Nov 5, 2024 at 3:27 PM Cindy Lu wrote:
>
> The vhost now uses vhost_task and workers as a child of the owner thread.
> While this aligns with containerization principles,it confuses some legacy
> userspace app, Therefore, we are reintroducing kthread API support.
>
> Introduce a new parame
The vhost now uses vhost_task and workers as a child of the owner thread.
While this aligns with containerization principles,it confuses some legacy
userspace app, Therefore, we are reintroducing kthread API support.
Introduce a new parameter to enable users to choose between
kthread and task mode
On Wed, 9 Oct 2024 at 16:20, Jason Wang wrote:
>
> On Wed, Oct 9, 2024 at 4:10 PM Stefano Garzarella wrote:
> >
> > On Wed, Oct 09, 2024 at 03:28:19PM GMT, Jason Wang wrote:
> > >On Mon, Oct 7, 2024 at 9:31 PM Stefano Garzarella
> > >wrote:
> > >>
> > >> On Fri, Oct 04, 2024 at 09:58:15AM GMT,
ing back the previous
> behavior when we had kthreads, but why do we want that?
> Do you have examples where the new mechanism is causing problems?
>
> >
> >Add a new module parameter to allow userspace to select behaviour
> >between using kthread and task
> >
> &g
On Wed, Oct 9, 2024 at 4:10 PM Stefano Garzarella wrote:
>
> On Wed, Oct 09, 2024 at 03:28:19PM GMT, Jason Wang wrote:
> >On Mon, Oct 7, 2024 at 9:31 PM Stefano Garzarella
> >wrote:
> >>
> >> On Fri, Oct 04, 2024 at 09:58:15AM GMT, Cindy Lu wrote:
> >> >The vhost is now using vhost_task and work
On Wed, Oct 09, 2024 at 03:28:19PM GMT, Jason Wang wrote:
On Mon, Oct 7, 2024 at 9:31 PM Stefano Garzarella wrote:
On Fri, Oct 04, 2024 at 09:58:15AM GMT, Cindy Lu wrote:
>The vhost is now using vhost_task and working as a child of the owner thread.
>While this makes sense from containerizatio
On Mon, Oct 7, 2024 at 9:31 PM Stefano Garzarella wrote:
>
> On Fri, Oct 04, 2024 at 09:58:15AM GMT, Cindy Lu wrote:
> >The vhost is now using vhost_task and working as a child of the owner thread.
> >While this makes sense from containerization POV, some old userspace is
> >confused, as previousl
using problems?
Add a new module parameter to allow userspace to select behaviour
between using kthread and task
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index 9ac25d08f473..a4a0bc34f59b 1
use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Cindy-Lu/vhost-Add-a-new-modparam-to-allow-userspace-select-vhost_task/20241004-100307
base: https://git.kernel.org/pub/scm/linux/kern
a new module parameter to allow userspace to select behaviour
between using kthread and task
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index 9ac25d08f473..a4a0bc34f59b 100644
--- a
@@ config QCOM_PIL_INFO
config QCOM_RPROC_COMMON
tristate
+ select AUXILIARY_BUS
config QCOM_Q6V5_COMMON
tristate
Reviewed-by: Chris Lew
ROC_COMMON
tristate
+ select AUXILIARY_BUS
config QCOM_Q6V5_COMMON
tristate
--
2.39.2
On Tue, 2023-09-12 at 22:32 +0300, Jarkko Sakkinen wrote:
> On Tue Sep 12, 2023 at 10:22 PM EEST, Mimi Zohar wrote:
> > On Tue, 2023-09-12 at 12:49 +0300, Jarkko Sakkinen wrote:
> > > On Tue Sep 12, 2023 at 10:41 AM EEST, Michal Suchánek wrote:
> > > > On Mon, Sep 11, 2023 at 11:39:38PM -0400, Nayn
On Tue Sep 12, 2023 at 10:22 PM EEST, Mimi Zohar wrote:
> On Tue, 2023-09-12 at 12:49 +0300, Jarkko Sakkinen wrote:
> > On Tue Sep 12, 2023 at 10:41 AM EEST, Michal Suchánek wrote:
> > > On Mon, Sep 11, 2023 at 11:39:38PM -0400, Nayna wrote:
> > > >
> > > > On 9/7/23 13:32, Michal Suchánek wrote:
On Tue, 2023-09-12 at 12:49 +0300, Jarkko Sakkinen wrote:
> On Tue Sep 12, 2023 at 10:41 AM EEST, Michal Suchánek wrote:
> > On Mon, Sep 11, 2023 at 11:39:38PM -0400, Nayna wrote:
> > >
> > > On 9/7/23 13:32, Michal Suchánek wrote:
> > > > Adding more CC's from the original patch, looks like get_m
On Tue Sep 12, 2023 at 6:39 AM EEST, Nayna wrote:
>
> On 9/7/23 13:32, Michal Suchánek wrote:
> > Adding more CC's from the original patch, looks like get_maintainers is
> > not that great for this file.
> >
> > On Thu, Sep 07, 2023 at 06:52:19PM +0200, Michal Suchanek wrote:
> >> No other platform
y/integrity/Kconfig
> > > > +++ b/security/integrity/Kconfig
> > > > @@ -68,8 +68,6 @@ config INTEGRITY_MACHINE_KEYRING
> > > > depends on INTEGRITY_ASYMMETRIC_KEYS
> > > > depends on SYSTEM_BLACKLIST_KEYRING
> > > > depend
On Tue Sep 12, 2023 at 10:41 AM EEST, Michal Suchánek wrote:
> On Mon, Sep 11, 2023 at 11:39:38PM -0400, Nayna wrote:
> >
> > On 9/7/23 13:32, Michal Suchánek wrote:
> > > Adding more CC's from the original patch, looks like get_maintainers is
> > > not that great for this file.
> > >
> > > On Th
> > index 232191ee09e3..b6e074ac0227 100644
> > > --- a/security/integrity/Kconfig
> > > +++ b/security/integrity/Kconfig
> > > @@ -68,8 +68,6 @@ config INTEGRITY_MACHINE_KEYRING
> > > depends on INTEGRITY_ASYMMETRIC_KEYS
> > > depends on S
NE_KEYRING
> > depends on INTEGRITY_ASYMMETRIC_KEYS
> > depends on SYSTEM_BLACKLIST_KEYRING
> > depends on LOAD_UEFI_KEYS || LOAD_PPC_KEYS
> > - select INTEGRITY_CA_MACHINE_KEYRING if LOAD_PPC_KEYS
> > - select INTEGRITY_CA_MACHINE_KEYRING_MAX if LOAD_PPC_KEYS
> &
integrity/Kconfig
> > > +++ b/security/integrity/Kconfig
> > > @@ -68,8 +68,6 @@ config INTEGRITY_MACHINE_KEYRING
> > > depends on INTEGRITY_ASYMMETRIC_KEYS
> > > depends on SYSTEM_BLACKLIST_KEYRING
> > > depends on LOAD_UEFI
191ee09e3..b6e074ac0227 100644
--- a/security/integrity/Kconfig
+++ b/security/integrity/Kconfig
@@ -68,8 +68,6 @@ config INTEGRITY_MACHINE_KEYRING
depends on INTEGRITY_ASYMMETRIC_KEYS
depends on SYSTEM_BLACKLIST_KEYRING
depends on LOAD_UEFI_KEYS || LOAD_PPC_KEYS
-
/integrity/Kconfig
> @@ -68,8 +68,6 @@ config INTEGRITY_MACHINE_KEYRING
> depends on INTEGRITY_ASYMMETRIC_KEYS
> depends on SYSTEM_BLACKLIST_KEYRING
> depends on LOAD_UEFI_KEYS || LOAD_PPC_KEYS
> - select INTEGRITY_CA_MACHINE_KEYRING if LOAD_PPC_KEYS
> - select INTEGRITY_CA_MA
Now that the SRCU Kconfig option is unconditionally selected, there is
no longer any point in selecting it. Therefore, remove the "select SRCU"
Kconfig statements.
Signed-off-by: Paul E. McKenney
Cc: Dan Williams
Cc: Vishal Verma
Cc: Dave Jiang
Cc:
Acked-by: Dan Williams
Reviewe
On Thu, Jan 05, 2023 at 08:48:28AM -0800, Dan Williams wrote:
> Paul E. McKenney wrote:
> > Now that the SRCU Kconfig option is unconditionally selected, there is
> > no longer any point in selecting it. Therefore, remove the "select SRCU"
> > Kconfig statements.
Paul E. McKenney wrote:
> Now that the SRCU Kconfig option is unconditionally selected, there is
> no longer any point in selecting it. Therefore, remove the "select SRCU"
> Kconfig statements.
>
> Signed-off-by: Paul E. McKenney
> Cc: Dan Williams
> Cc: Visha
Now that the SRCU Kconfig option is unconditionally selected, there is
no longer any point in selecting it. Therefore, remove the "select SRCU"
Kconfig statements.
Signed-off-by: Paul E. McKenney
Cc: Dan Williams
Cc: Vishal Verma
Cc: Dave Jiang
Cc:
---
drivers/dax/Kconfig | 1
I thought about it carefully. Indeed, in my scenario(virtual machine which use
optane as DRAM), device assignment can be performed in userspace at very
early time after the system is started. This patch is not needed in my
scenario. Thank you for your reply.
Dan Williams 于2022年3月23日周三 10:01写道：
>
On Mon, Feb 28, 2022 at 1:50 AM Zhenguo Yao wrote:
>
> device_dax driver always match dax devices by default. The other
> drivers only match devices by dax_id. There are situations which
> need kmem drvier match all the dax device at boot time. So
> adding a parameter to support this function.
Wh
device_dax driver always match dax devices by default. The other
drivers only match devices by dax_id. There is situations which
need kmem drvier match all the dax device at boot time. So
adding a parameter to support this function.
Signed-off-by: Zhenguo Yao
---
Changes:
- v1->v2 fix bu
umented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Zhenguo-Yao/device-dax-Adding-match-parameter-to-select-which-driver-to-match-dax-devices/20220228-175040
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds
device_dax driver always match dax devices by default. The other
drivers only match devices by dax_id. There are situations which
need kmem drvier match all the dax device at boot time. So
adding a parameter to support this function.
Signed-off-by: Zhenguo Yao
---
drivers/dax/device.c | 3 +++
d
ly it was possible that this module was disabled while the
> enetc was enabled. Fix it by automatically select the enetc-ierb module.
>
> Fixes: e7d48e5fbf30 ("net: enetc: add a mini driver for the Integrated
> Endpoint Register Block")
> Signed-off-by: Michael Walle
&g
e
> enetc was enabled. Fix it by automatically select the enetc-ierb module.
>
> Fixes: e7d48e5fbf30 ("net: enetc: add a mini driver for the Integrated
> Endpoint Register Block")
> Signed-off-by: Michael Walle
> ---
Acked-by: Vladimir Oltean
mp_rmb() in reuseport_(select|migrate)_sock() */
smp_wmb();
reuse->num_socks++;
}
@@ -435,6 +435,23 @@ static struct sock *run_bpf_filter(struct sock_reuseport
*reuse, u16 socks,
return reuse->socks[index];
}
+static struct sock *reuseport_select_sock_by_hash(stru
Now that enetc supports flow control we have to make sure the settings in
the IERB are correct. Therefore, we actually depend on the enetc-ierb
module. Previously it was possible that this module was disabled while the
enetc was enabled. Fix it by automatically select the enetc-ierb module.
Fixes
), then the IIO_TRIGGERED_BUFFER symbol isn't
> > selected/enforced.
> >
> > Previously, each driver would enforce/select the IIO_TRIGGERED_BUFFER
> > symbol. With this change the HID_SENSOR_IIO_TRIGGER (for the
> > hid-sensor-trigger module) will enforce that IIO_TRI
Committer: Peter Zijlstra
CommitterDate: Fri, 16 Apr 2021 17:06:33 +02:00
sched: Don't make LATENCYTOP select SCHED_DEBUG
SCHED_DEBUG is not in fact required for LATENCYTOP, don't select it.
Suggested-by: Mel Gorman
Signed-off-by: Peter Zijlstra (Intel)
Tested-by: Valentin Schneider
L
module.
>
> The above change works fine, if any of the sensors get built.
> However, when
> only the common hid-sensor-trigger module gets built (and none of the
> drivers), then the IIO_TRIGGERED_BUFFER symbol isn't
> selected/enforced.
>
> Previously, each driver would enf
n
only the common hid-sensor-trigger module gets built (and none of the
drivers), then the IIO_TRIGGERED_BUFFER symbol isn't selected/enforced.
Previously, each driver would enforce/select the IIO_TRIGGERED_BUFFER
symbol. With this change the HID_SENSOR_IIO_TRIGGER (for the
hid-sensor-trigg
That line was using tab + 4 spaces on the left and was reformatted to
use 2 tabs.
If you don't like it I've uploaded patch v5 not touching that line.
On Tue, Apr 13, 2021 at 5:34 AM Bastien Nocera wrote:
>
> On Tue, 2021-04-13 at 01:02 +, Chris Ye wrote:
> > Add
Add "Select" button input capability and input event mapping for
Microsoft Xbox One controller. From product site this is also referred as
"Share" button.
Fixed Microsoft Xbox One controller select button not working under USB
connection.
Signed-off-by: Chris Ye
---
dr
On Tue, 2021-04-13 at 01:02 +, Chris Ye wrote:
> Add "Select" button input capability and input event mapping for
> Microsoft Xbox One controller. From product site this is also
> referred as
> "Share" button.
> Fixed Microsoft Xbox One controller se
Add "Select" button input capability and input event mapping for
Microsoft Xbox One controller. From product site this is also referred as
"Share" button.
Fixed Microsoft Xbox One controller select button not working under USB
connection.
Signed-off-by: Chris Ye
---
dr
SCHED_DEBUG is not in fact required for LATENCYTOP, don't select it.
Suggested-by: Mel Gorman
Signed-off-by: Peter Zijlstra (Intel)
---
lib/Kconfig.debug |1 -
1 file changed, 1 deletion(-)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1670,7 +1670,6 @@ config LATEN
bool "Aspeed display driver"
select DRM_WANT_CMA
config DRM_WANT_CMA
bool
help
Select this from any driver that benefits from CMA being enabled
config DMA_CMA
bool "Use CMA helpers for DRM"
default DRM_WANT_C
On 08.04.21 15:19, Arnd Bergmann wrote:
On Thu, Apr 8, 2021 at 2:50 PM Linus Walleij wrote:
On Thu, Apr 8, 2021 at 2:01 PM David Hildenbrand wrote:
This is something you could do using a hidden helper symbol like
config DRMA_ASPEED_GFX
bool "Aspeed display driver"
Add PHY input reference clock frequency as a new dimension to select proper
register configuration.
Signed-off-by: Swapnil Jakhade
---
drivers/phy/cadence/phy-cadence-torrent.c | 830 +++---
1 file changed, 422 insertions(+), 408 deletions(-)
diff --git a/drivers/phy/cadence
On Thu, Apr 8, 2021 at 6:44 PM David Hildenbrand wrote:
> > drivers/gpu/drm/mcde/Kconfig
> > drivers/gpu/drm/pl111/Kconfig
> > drivers/gpu/drm/tve200/Kconfig
>
> I was assuming these are "real" dependencies. Will it also work without
> DMA_CMA?
It will mostly work but that is only because the re
config DRMA_ASPEED_GFX
> >>> bool "Aspeed display driver"
> >>> select DRM_WANT_CMA
> >>>
> >>> config DRM_WANT_CMA
> >>> bool
> >>> help
> >>>
On Thu, Apr 08, 2021 at 01:38:17PM +0200, Daniel Vetter wrote:
> If you want to change this, we need automatic conflict resolution like apt
> and other package managers have, with suggestions how to fix the config if
> you want to enable a driver, but some of its requirements are missing. The
> cu
On 08.04.21 14:49, Linus Walleij wrote:
On Thu, Apr 8, 2021 at 2:01 PM David Hildenbrand wrote:
This is something you could do using a hidden helper symbol like
config DRMA_ASPEED_GFX
bool "Aspeed display driver"
select DRM_WANT_CMA
config DRM_WANT_CMA
On Thu, Apr 8, 2021 at 2:50 PM Linus Walleij wrote:
>
> On Thu, Apr 8, 2021 at 2:01 PM David Hildenbrand wrote:
>
> > > This is something you could do using a hidden helper symbol like
> > >
> > > config DRMA_ASPEED_GFX
> > > bool "Aspeed
On Thu, Apr 8, 2021 at 2:01 PM David Hildenbrand wrote:
> > This is something you could do using a hidden helper symbol like
> >
> > config DRMA_ASPEED_GFX
> > bool "Aspeed display driver"
> > select DRM_WANT_CMA
> >
> > c
which drivers are enabled?
>
> "Random drivers should not override a user configuration of core knobs
> (e.g., CONFIG_DMA_CMA=n)."
>
> Let's assume I'm a distribution and want to set CONFIG_CMA=n or want to
> set CONFIG_DMA_CMA=n with CONFIG_CMA=y; there is no wa
with
e.g., DRMA_ASPEED_GFX=y because it will always override my (user!)
setting -- even though it doesn't really always need it. Using "select"
is the problem here.
This is something you could do using a hidden helper symbol like
config DRMA_ASPEED_GFX
bool "Aspeed
eful default for DMA_CMA depending on which drivers are enabled?
This is something you could do using a hidden helper symbol like
config DRMA_ASPEED_GFX
bool "Aspeed display driver"
select DRM_WANT_CMA
config DRM_WANT_CMA
bool
help
Select this from
ect
> > dependencies and manual overrides.
> >
> > "This is similar to "select" as it enforces a lower limit on another
> > symbol except that the "implied" symbol's value may still be set to n
> > from a direct dependency or wi
In particular, it does not prevent a configuration with 'DRM_CMA=m'
I assume you meant "DRM_CMA=n" ? DRM_CMA cannot be built as a module.
Ok, at least that makes it easier.
and 'DRMA_ASPEED_GFX=y', or any build failures from such
a configuration.
I don't follow. "DRM_CMA=n" and 'DRMA_ASPEE
_DMA_CMA=n). Use "imply" instead, to still respect
> >> dependencies and manual overrides.
> >>
> >> "This is similar to "select" as it enforces a lower limit on another
> >> symbol except that the "implied" symbol's v
encies and manual overrides.
"This is similar to "select" as it enforces a lower limit on another
symbol except that the "implied" symbol's value may still be set to n
from a direct dependency or with a visible prompt."
Implying DRM_CMA should be sufficient
s is similar to "select" as it enforces a lower limit on another
symbol except that the "implied" symbol's value may still be set to n
from a direct dependency or with a visible prompt."
Implying DRM_CMA should be sufficient, as that depends on CMA.
Note: If this is
On 4/7/21 8:13 PM, Alexandre Belloni wrote:
> Hi,
>
> On 07/04/2021 20:00:53+0300, Eugen Hristev wrote:
>> From: Claudiu Beznea
>>
>> Select PLL, generic clock and UTMI support for SAMA7G5.
>>
>> Signed-off-by: Claudiu Beznea
>> Signed-off-by:
On Thu, Apr 8, 2021 at 11:22 AM David Hildenbrand wrote:
>
> Random drivers should not override a user configuration of core knobs
> (e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
> dependencies and manual overrides.
>
> "This is similar to &quo
On Thu, Apr 08, 2021 at 12:05:21PM +0200, David Hildenbrand wrote:
> Trying to set CONFIG_CMA=y with CONFIG_DMA_CMA=n revealed that we have
> three drivers that select these options. Random drivers should not
> override user settings of such core knobs. Let's use "imply DMA_C
Random drivers should not override a user configuration of core knobs
(e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
dependencies and manual overrides.
"This is similar to "select" as it enforces a lower limit on another
symbol except that the "imp
Random drivers should not override a user configuration of core knobs
(e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
dependencies and manual overrides.
"This is similar to "select" as it enforces a lower limit on another
symbol except that the "imp
Trying to set CONFIG_CMA=y with CONFIG_DMA_CMA=n revealed that we have
three drivers that select these options. Random drivers should not
override user settings of such core knobs. Let's use "imply DMA_CMA"
instead, such that user configuration and dependencies are respected.
This is similar to "select" as it enforces a lower limit on another
symbol except that the "implied" symbol's value may still be set to n
from a direct dependency or with a visible prompt."
Implying DRM_CMA should be sufficient, as that depends on CMA.
^
On Thu, Apr 08, 2021 at 11:20:11AM +0200, David Hildenbrand wrote:
> Random drivers should not override a user configuration of core knobs
> (e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
> dependencies and manual overrides.
>
> "This is similar to &
On Thu, Apr 08, 2021 at 11:20:10AM +0200, David Hildenbrand wrote:
> Random drivers should not override a user configuration of core knobs
> (e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
> dependencies and manual overrides.
>
> "This is similar to &
Random drivers should not override a user configuration of core knobs
(e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
dependencies and manual overrides.
"This is similar to "select" as it enforces a lower limit on another
symbol except that the "imp
Random drivers should not override a user configuration of core knobs
(e.g., CONFIG_DMA_CMA=n). Use "imply" instead, to still respect
dependencies and manual overrides.
"This is similar to "select" as it enforces a lower limit on another
symbol except that the "imp
Trying to set CONFIG_CMA=y with CONFIG_DMA_CMA=n revealed that we have
three drivers that select these options. Random drivers should not
override user settings of such core knobs. Let's use "imply DMA_CMA"
instead, such that user configuration and dependencies are respected.
Cc: J
Hey Zhang,
On Thu, 8 Apr 2021 at 09:10, zhangjianhua (E) wrote:
>
> Hello Robert
>
> I am sorry that I make a mistake about the compiling error of lt8912b,
>
> the reason is that lt8912b miss the header file .
>
> Although there are many files reference gpiod_set_value_cansleep() and
>
> devm_gpi
Hello Robert
I am sorry that I make a mistake about the compiling error of lt8912b,
the reason is that lt8912b miss the header file .
Although there are many files reference gpiod_set_value_cansleep() and
devm_gpiod_get_optional(), they all include
and not occur the compiling error like lt89
t;
> Link:
> https://lore.kernel.org/linux-kbuild/20210313194836.372585-11-masahi...@kernel.org/
> Fixes: commit a8c0f1c634507 ("MIPS: Select ARCH_KEEP_MEMBLOCK if
s/commit //
> DEBUG_KERNEL to enable sysfs memblock debug")
> Cc: Masahiro Yamada
> Reported-by: Guente
; https://lore.kernel.org/linux-kbuild/20210313194836.372585-11-masahi...@kernel.org/
> Fixes: commit a8c0f1c634507 ("MIPS: Select ARCH_KEEP_MEMBLOCK if
> DEBUG_KERNEL to enable sysfs memblock debug")
> Cc: Masahiro Yamada
Please replace it with:
Reviewed-by: Masahiro Yama
.
allnoconfig disables DEBUG_KERNEL and thus ARCH_KEEP_MEMBLOCK, which
changes __init_memblock to be equivalent to __meminit triggering the
above error.
Link:
https://lore.kernel.org/linux-kbuild/20210313194836.372585-11-masahi...@kernel.org/
Fixes: commit a8c0f1c634507 ("MIPS: Select ARCH_KEEP_MEMBLO
Hi,
On 07/04/2021 20:00:53+0300, Eugen Hristev wrote:
> From: Claudiu Beznea
>
> Select PLL, generic clock and UTMI support for SAMA7G5.
>
> Signed-off-by: Claudiu Beznea
> Signed-off-by: Eugen Hristev
> ---
> arch/arm/mach-at91/Kconfig | 3 +++
> 1 file changed
From: Claudiu Beznea
Select PLL, generic clock and UTMI support for SAMA7G5.
Signed-off-by: Claudiu Beznea
Signed-off-by: Eugen Hristev
---
arch/arm/mach-at91/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-at91/Kconfig b/arch/arm/mach-at91/Kconfig
index
Thanks, I will do that.
在 2021/4/7 16:03, Robert Foss 写道:
Yes, you are right, there are many files reference
gpiod_set_value_cansleep() and
devm_gpiod_get_optional(). How about add config dependencies for all
releated
I think this is the way to go and roughly half of the drm bridge
drivers see
> Yes, you are right, there are many files reference
> gpiod_set_value_cansleep() and
>
> devm_gpiod_get_optional(). How about add config dependencies for all
> releated
I think this is the way to go and roughly half of the drm bridge
drivers seem to need this change.
Do you mind submitting a ser
/gpu/drm/bridge/Kconfig
index dba62f92d051..caa9658ec933 100644
--- a/drivers/gpu/drm/bridge/Kconfig
+++ b/drivers/gpu/drm/bridge/Kconfig
@@ -67,6 +67,7 @@ config DRM_LONTIUM_LT8912B
select DRM_PANEL_BRIDGE
select DRM_KMS_HELPER
select REGMAP_I2C
+ select GPIOLIB
This
1 - 100 of 3213 matches
Mail list logo
