From: Jon Hunter <jonathanh@nvidia.com>
To: Peter Robinson <pbrobinson@gmail.com>, linux-tegra@vger.kernel.org
Cc: Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH] bus: tegra-aconnect: Update dependency to ARCH_TEGRA
Date: Fri, 12 Jan 2024 06:53:14 +0000 [thread overview]
Message-ID: <e7cf5ce1-c7e9-443b-a005-fed550a5bf3f@nvidia.com> (raw)
In-Reply-To: <20240111190327.198794-1-pbrobinson@gmail.com>
On 11/01/2024 19:03, Peter Robinson wrote:
> Update the architecture dependency to be the generic Tegra
> because the driver works on the four latest Tegra generations
> not just T210, if you build a kernel with a specific
> ARCH_TEGRA_xxx_SOC optioon that excludes 210 you don't get
> this driver.
Same typo for 'optioon'
> Fixes: 46a88534afb59 ("bus: Add support for Tegra ACONNECT")
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> Cc: Jon Hunter <jonathanh@nvidia.com>
> Cc: Thierry Reding <treding@nvidia.com>
> ---
> drivers/bus/Kconfig | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/bus/Kconfig b/drivers/bus/Kconfig
> index e6742998f372c..b003dad62d596 100644
> --- a/drivers/bus/Kconfig
> +++ b/drivers/bus/Kconfig
> @@ -186,11 +186,12 @@ config SUNXI_RSB
>
> config TEGRA_ACONNECT
> tristate "Tegra ACONNECT Bus Driver"
> - depends on ARCH_TEGRA_210_SOC
> + depends on ARCH_TEGRA
> depends on OF && PM
> help
> Driver for the Tegra ACONNECT bus which is used to interface with
> - the devices inside the Audio Processing Engine (APE) for Tegra210.
> + the devices inside the Audio Processing Engine (APE) for
> + Tegra210/Tegra186/Tegra194/Tegra234.
>
> config TEGRA_GMI
> tristate "Tegra Generic Memory Interface bus driver"
Otherwise ...
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Jon
--
nvpublic
prev parent reply other threads:[~2024-01-12 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 19:03 [PATCH] bus: tegra-aconnect: Update dependency to ARCH_TEGRA Peter Robinson
2024-01-12 6:53 ` Jon Hunter [this message]
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=e7cf5ce1-c7e9-443b-a005-fed550a5bf3f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=treding@nvidia.com \
/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