arm64: defconfig: Enable HDA INTEL config for ARM64
PATCH v2 1/1 arm64: defconfig: Enable HDA INTEL config for ARM64
Enable CONFIG_SND_HDA_INTEL for NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.
--- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm64/configs/defconfig +1 -0
@@ -812,6 +812,7 @@ CONFIG_LOGO=y CONFIG_SOUND=y CONFIG_SND=y CONFIG_SND_ALOOP=m +CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_TEGRA=m CONFIG_SND_HDA_CODEC_HDMI=m CONFIG_SND_SOC=y
Signature · 7 lines
2.17.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.
It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 11 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
Quoted 4 lines
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 9 lines · Mohan Kumar D
Quoted 7 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.
Quoted 6 lines
Quoted 4 lines
It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 8 lines · Mohan Kumar D
Quoted 7 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Quoted 4 lines
Best regards,
Krzysztof
Quoted 18 lines · Mohan Kumar D
Quoted 16 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 12 lines · Mohan Kumar D
Quoted 11 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Again, we do not enable drivers for every PCI card.
Best regards,
Krzysztof
Quoted 22 lines · Krzysztof Kozlowski
Quoted 13 lines · Mohan Kumar D
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 10 lines · Mohan Kumar D
Quoted 9 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Quoted 5 lines
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Again, we do not enable drivers for every PCI card.
I don't think we have any set rules for what goes in a defconfig. If one has a real use-case, we tend to enable stuff in defconfig, especially if it's a module.
Signature · 1 line
Catalin
Quoted 27 lines · Catalin Marinas
Quoted 26 lines · Krzysztof Kozlowski
Quoted 13 lines · Mohan Kumar D
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 10 lines · Mohan Kumar D
Quoted 9 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Quoted 5 lines
Quoted 1 line
Again, we do not enable drivers for every PCI card.
I don't think we have any set rules for what goes in a defconfig. If one has a real use-case, we tend to enable stuff in defconfig, especially if it's a module.
There will be always an use case for every PCI and USB card. It's not related to storage or networking which could justify device bringup (rootfs). It's really not needed for any board operation. defconfig is not for marketing products but for our development and reference platforms.
The only argument behind this change is "I have a PCI card and I want it in defconfig", but why it has to be in defconfig in the first place? There is no reason. This is not distro...
Best regards,
Krzysztof
Quoted 30 lines · Krzysztof Kozlowski
Quoted 29 lines · Catalin Marinas
Quoted 27 lines · Krzysztof Kozlowski
Quoted 13 lines · Mohan Kumar D
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 10 lines · Mohan Kumar D
Quoted 9 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Again, we do not enable drivers for every PCI card.
Quoted 8 lines
Quoted 3 lines
I don't think we have any set rules for what goes in a defconfig. If one has a real use-case, we tend to enable stuff in defconfig, especially if it's a module.
There will be always an use case for every PCI and USB card. It's not related to storage or networking which could justify device bringup (rootfs). It's really not needed for any board operation. defconfig is not for marketing products but for our development and reference platforms.
If defconfig were only for boot-critical drivers, it's terribly bloated as it is. We enable things like multimedia, infrared and audio. None of those are critical to booting a system. Heck, we also enable most of DRM/KMS, which are useful for boot on consumer devices, but are rarely critical on development and reference platforms.
Besides, a PCI board can be considered a development platform depending on who you are.
I've always looked at defconfig as more of a guideline as to what's a useful baseline configuration for an architecture.
Quoted 3 lines
The only argument behind this change is "I have a PCI card and I want it in defconfig", but why it has to be in defconfig in the first place? There is no reason. This is not distro...
That's highly subjective and honestly that argument can go in both directions. People can, after all, start from an allnoconfig and then work their way up to something that's usable on their particular device. Or they could start from an allmodconfig and work their way down.
The point of defconfig is to give you something that's somewhere between the two extremes. Obviously if we start enabling everything, it defeats that purpose. If we prohibit the enablement of new options, we equally limit its usefulness.
Thierry
Quoted 35 lines · Thierry Reding
Quoted 34 lines · Krzysztof Kozlowski
Quoted 32 lines · Catalin Marinas
Quoted 22 lines · Krzysztof Kozlowski
Quoted 13 lines · Mohan Kumar D
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 10 lines · Mohan Kumar D
Quoted 9 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Quoted 5 lines
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Again, we do not enable drivers for every PCI card.
I don't think we have any set rules for what goes in a defconfig. If one has a real use-case, we tend to enable stuff in defconfig, especially if it's a module.
Quoted 6 lines
Quoted 4 lines
There will be always an use case for every PCI and USB card. It's not related to storage or networking which could justify device bringup (rootfs). It's really not needed for any board operation. defconfig is not for marketing products but for our development and reference platforms.
If defconfig were only for boot-critical drivers, it's terribly bloated
We enable drivers for devices present in our platforms. Everything which is on such platforms. For pluggable USB/PCI/whatever third-party devices, then comes the argument as boot-related.
Quoted 10 lines
as it is. We enable things like multimedia, infrared and audio. None of those are critical to booting a system. Heck, we also enable most of DRM/KMS, which are useful for boot on consumer devices, but are rarely critical on development and reference platforms.
Besides, a PCI board can be considered a development platform depending on who you are.
I've always looked at defconfig as more of a guideline as to what's a useful baseline configuration for an architecture.
Yep and this one here is nowhere near that architecture. It's pluggable card, not related to hardware nor arm64 (If I understood correctly). Why you do not enable it on x86? Or multi_v7? or hundreds of other defconfigs?
Quoted 9 lines
Quoted 4 lines
The only argument behind this change is "I have a PCI card and I want it in defconfig", but why it has to be in defconfig in the first place? There is no reason. This is not distro...
That's highly subjective and honestly that argument can go in both directions. People can, after all, start from an allnoconfig and then work their way up to something that's usable on their particular device. Or they could start from an allmodconfig and work their way down.
I am sorry, but adding new stuff does not require arguments against. Adding new stuff requires argument for it. You reverse the argumentation that I need to find proves that we do not need it in mainline platforms, if I got your response correctly.
Quoted 5 lines
The point of defconfig is to give you something that's somewhere between the two extremes. Obviously if we start enabling everything, it defeats that purpose. If we prohibit the enablement of new options, we equally limit its usefulness.
I don't think we discuss the same thing. There are no extremes here at all. The patch is about enabling arm64-unrelated PCI pluggable device, just because it came from @nvidia.com author. If you think some PCI pluggable 3rd party device is suitable for defconfig, I will bring hundreds of other drivers I am also plugging over PCI to my boards, just because I want some audio.
It's not reasonable path...
Best regards,
Krzysztof
Quoted 55 lines · Krzysztof Kozlowski
Quoted 35 lines · Thierry Reding
Quoted 34 lines · Krzysztof Kozlowski
Quoted 32 lines · Catalin Marinas
Quoted 22 lines · Krzysztof Kozlowski
Quoted 13 lines · Mohan Kumar D
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 10 lines · Mohan Kumar D
Quoted 9 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Quoted 5 lines
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Again, we do not enable drivers for every PCI card.
I don't think we have any set rules for what goes in a defconfig. If one has a real use-case, we tend to enable stuff in defconfig, especially if it's a module.
Quoted 6 lines
Quoted 4 lines
There will be always an use case for every PCI and USB card. It's not related to storage or networking which could justify device bringup (rootfs). It's really not needed for any board operation. defconfig is not for marketing products but for our development and reference platforms.
If defconfig were only for boot-critical drivers, it's terribly bloated
We enable drivers for devices present in our platforms. Everything which is on such platforms. For pluggable USB/PCI/whatever third-party devices, then comes the argument as boot-related.
Quoted 8 lines
as it is. We enable things like multimedia, infrared and audio. None of those are critical to booting a system. Heck, we also enable most of DRM/KMS, which are useful for boot on consumer devices, but are rarely critical on development and reference platforms.
Besides, a PCI board can be considered a development platform depending on who you are.
Quoted 6 lines
Quoted 2 lines
I've always looked at defconfig as more of a guideline as to what's a useful baseline configuration for an architecture.
Yep and this one here is nowhere near that architecture. It's pluggable card, not related to hardware nor arm64 (If I understood correctly). Why you do not enable it on x86? Or
multi_v7? or hundreds of other defconfigs?
My understanding is that the code behind SND_HDA_INTEL, despite the name, is in fact generic PCI HDA code and is compatible with a number of non-Intel devices. It's also nothing x86-specific because this code works on any PCI-enabled platform (it's for driving generic PCI HDA controllers).
It's quite common for people to hook up PCI cards on NVIDIA Jetson platforms (which are arm64). Often these will be NVIDIA GPUs, but they can be any brand of GPU, really (SND_HDA_INTEL supports hardware from a large number of vendors).
Quoted 9 lines
Quoted 8 lines
Quoted 3 lines
The only argument behind this change is "I have a PCI card and I want it in defconfig", but why it has to be in defconfig in the first place? There is no reason. This is not distro...
That's highly subjective and honestly that argument can go in both directions. People can, after all, start from an allnoconfig and then work their way up to something that's usable on their particular device. Or they could start from an allmodconfig and work their way down.
Quoted 4 lines
I am sorry, but adding new stuff does not require arguments against. Adding new stuff requires argument for it. You reverse the argumentation that I need to find proves that we do not need it in mainline platforms, if I got your response correctly.
Adding new stuff also doesn't require arguments in favour. At least that's not been my experience in kernel development. If somebody spends the time to write a driver, we don't tend to ask proof of why it's useful, we trust that they wouldn't have spent the effort if they didn't think it worth it.
Besides, this is to enable support for these various HDA controllers that can be plugged into Jetson platforms, which very well are mainline platforms.
Quoted 8 lines
Quoted 4 lines
The point of defconfig is to give you something that's somewhere between the two extremes. Obviously if we start enabling everything, it defeats that purpose. If we prohibit the enablement of new options, we equally limit its usefulness.
I don't think we discuss the same thing. There are no extremes here at all. The patch is about enabling arm64-unrelated PCI pluggable device, just because it came from @nvidia.com author. If you think some PCI
I think you're making this into something it's not. What would be the benefit for NVIDIA to enable something that is unused? If there's consensus that only boot-critical pieces should go into defconfig, then that's fine with me. Currently that's not the case, so painting this as some sort of marketing stunt is hardly fair.
Quoted 5 lines
pluggable 3rd party device is suitable for defconfig, I will bring hundreds of other drivers I am also plugging over PCI to my boards, just because I want some audio.
It's not reasonable path...
Well, then what is a reasonable path? We've had per-platform defconfigs on 32-bit ARM and people weren't happy about those. But if the single defconfig on 64-bit ARM doesn't generate a configuration that is useful for many people, then we don't need it. People could then just keep their own, local default configurations.
Surely I'm not the only one that gets annoyed if I have to tweak config and rebuild multiple times until I have the right configuration.
Thierry
Quoted 69 lines · Thierry Reding
Quoted 55 lines · Krzysztof Kozlowski
Quoted 35 lines · Thierry Reding
Quoted 34 lines · Krzysztof Kozlowski
Quoted 32 lines · Catalin Marinas
Quoted 22 lines · Krzysztof Kozlowski
Quoted 13 lines · Mohan Kumar D
Quoted 12 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 10 lines · Mohan Kumar D
Quoted 9 lines · Krzysztof Kozlowski
External email: Use caution opening links or attachments
Quoted 3 lines · Mohan Kumar
Enable
CONFIG_SND_HDA_INTELfor NVIDIA PCI based graphics sound card for ARM64 based platforms as Intel PCI driver was used for registering the sound card.It's not a part of SoC, not a common device used during debugging or development, so I don't think it is reasonable to enable it. We do not enable driver just because someone uses them. Otherwise please clarify which board has this device embedded (not pluggable by user, but embedded).
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This change is required for enabling HDA sound registration for Nvidia discrete GPU cards based on PCI and pluggable to Nvidia Jetson Platforms.
You can plug anything to PCI slot and we do not enable every such PCI adapter.
Without this config enabled, the Intel hda audio driver won't be built and dGPU won't be able to register sound card. Do you have any suggestion here?
Quoted 5 lines
Without hundreds of other drivers they also won't be built and won't be usable. Anyway, this is just defconfig, so it does not matter. You can always enable it in your setup, why is this a problem?
Again, we do not enable drivers for every PCI card.
I don't think we have any set rules for what goes in a defconfig. If one has a real use-case, we tend to enable stuff in defconfig, especially if it's a module.
Quoted 6 lines
Quoted 4 lines
There will be always an use case for every PCI and USB card. It's not related to storage or networking which could justify device bringup (rootfs). It's really not needed for any board operation. defconfig is not for marketing products but for our development and reference platforms.
If defconfig were only for boot-critical drivers, it's terribly bloated
We enable drivers for devices present in our platforms. Everything which is on such platforms. For pluggable USB/PCI/whatever third-party devices, then comes the argument as boot-related.
Quoted 8 lines
as it is. We enable things like multimedia, infrared and audio. None of those are critical to booting a system. Heck, we also enable most of DRM/KMS, which are useful for boot on consumer devices, but are rarely critical on development and reference platforms.
Besides, a PCI board can be considered a development platform depending on who you are.
Quoted 6 lines
Quoted 2 lines
I've always looked at defconfig as more of a guideline as to what's a useful baseline configuration for an architecture.
Yep and this one here is nowhere near that architecture. It's pluggable card, not related to hardware nor arm64 (If I understood correctly). Why you do not enable it on x86? Or
multi_v7? or hundreds of other defconfigs?My understanding is that the code behind
SND_HDA_INTEL, despite the name, is in fact generic PCI HDA code and is compatible with a number of non-Intel devices. It's also nothing x86-specific because this code works on any PCI-enabled platform (it's for driving generic PCI HDA controllers).
Quoted 4 lines
It's quite common for people to hook up PCI cards on NVIDIA Jetson platforms (which are arm64). Often these will be NVIDIA GPUs, but they can be any brand of GPU, really (
SND_HDA_INTELsupports hardware from a large number of vendors).
Like with every other board with PCI or miniPCI slots. You can hook up there anything and we do not enable all these possible devices.
Quoted 15 lines
Quoted 10 lines
Quoted 9 lines
Quoted 4 lines
The only argument behind this change is "I have a PCI card and I want it in defconfig", but why it has to be in defconfig in the first place? There is no reason. This is not distro...
That's highly subjective and honestly that argument can go in both directions. People can, after all, start from an allnoconfig and then work their way up to something that's usable on their particular device. Or they could start from an allmodconfig and work their way down.
Quoted 4 lines
I am sorry, but adding new stuff does not require arguments against. Adding new stuff requires argument for it. You reverse the argumentation that I need to find proves that we do not need it in mainline platforms, if I got your response correctly.
Quoted 5 lines
Adding new stuff also doesn't require arguments in favour. At least that's not been my experience in kernel development. If somebody spends the time to write a driver, we don't tend to ask proof of why it's useful, we trust that they wouldn't have spent the effort if they didn't think it worth it.
We need that argument and submitter provides - I have a device for it. That's the argument for including driver in the kernel. That's not an argument good enough for including in defconfig, though.
Quoted 13 lines
Besides, this is to enable support for these various HDA controllers that can be plugged into Jetson platforms, which very well are mainline platforms.
Quoted 8 lines
Quoted 4 lines
The point of defconfig is to give you something that's somewhere between the two extremes. Obviously if we start enabling everything, it defeats that purpose. If we prohibit the enablement of new options, we equally limit its usefulness.
I don't think we discuss the same thing. There are no extremes here at all. The patch is about enabling arm64-unrelated PCI pluggable device, just because it came from @nvidia.com author. If you think some PCI
Quoted 5 lines
I think you're making this into something it's not. What would be the benefit for NVIDIA to enable something that is unused? If there's consensus that only boot-critical pieces should go into defconfig, then that's fine with me. Currently that's not the case, so painting this as some sort of marketing stunt is hardly fair.
As I said - no one here speaks about boot-critical pieces. We enable everything which is on the boards. Everything.
Now for fully user pluggable, common devices - like USB, PCI - we enable stuff relevant to the boot.
Quoted 5 lines
Quoted 5 lines
pluggable 3rd party device is suitable for defconfig, I will bring hundreds of other drivers I am also plugging over PCI to my boards, just because I want some audio.
Quoted 7 lines
Quoted 1 line
It's not reasonable path...
Well, then what is a reasonable path? We've had per-platform defconfigs on 32-bit ARM and people weren't happy about those. But if the single defconfig on 64-bit ARM doesn't generate a configuration that is useful for many people, then we don't need it. People could then just keep their own, local default configurations.
And what is the problem with it? It's just defconfig, so what's the big deal for them to have out of tree patch?
For me it is big deal because I am using and building defconfig all the time. It uses my electricity, so directly my money. It uses my time, which is even more important than money.
If anyone wants user-pluggable devices, please add fragments or one more defconfig, so I won't be affected by such drivers.
Quoted 5 lines
Surely I'm not the only one that gets annoyed if I have to tweak config and rebuild multiple times until I have the right configuration.
Thierry
Best regards,
Krzysztof