linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mohan Kumar <mkumard@nvidia.com>,
	catalin.marinas@arm.com, will@kernel.org,
	dmitry.baryshkov@linaro.org, shawnguo@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, treding@nvidia.com,
	jonathanh@nvidia.com
Subject: Re: [PATCH v2] arm64: defconfig: Enable HDA INTEL config for ARM64
Date: Wed, 18 Jan 2023 08:34:40 +0100	[thread overview]
Message-ID: <e871dae2-58ac-7ad9-c198-c4e90d26c69b@linaro.org> (raw)
In-Reply-To: <20230117181658.17010-1-mkumard@nvidia.com>

On 17/01/2023 19:16, Mohan Kumar wrote:
> 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.

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


  reply	other threads:[~2023-01-18  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 18:16 [PATCH v2] arm64: defconfig: Enable HDA INTEL config for ARM64 Mohan Kumar
2023-01-18  7:34 ` Krzysztof Kozlowski [this message]
2023-01-18 11:46   ` Mohan Kumar D
2023-01-18 12:36     ` Krzysztof Kozlowski
2023-01-20  5:48       ` Mohan Kumar D
2023-01-20  6:20         ` Krzysztof Kozlowski
2023-01-20 16:56           ` Catalin Marinas
2023-01-20 17:00             ` Krzysztof Kozlowski
2023-01-23 15:58               ` Thierry Reding
2023-01-23 16:05                 ` Krzysztof Kozlowski
2023-01-23 17:26                   ` Thierry Reding
2023-01-23 17:34                     ` Krzysztof Kozlowski

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=e871dae2-58ac-7ad9-c198-c4e90d26c69b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=shawnguo@kernel.org \
    --cc=treding@nvidia.com \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).