From: YueHaibing <yuehaibing@huawei.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<digetx@gmail.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] soc/tegra: fuse: Add missing DMADEVICES dependency
Date: Wed, 29 Jun 2022 09:43:52 +0800 [thread overview]
Message-ID: <83392db3-e8d1-e839-3cb6-e90e14044a56@huawei.com> (raw)
In-Reply-To: <53794ec1-c9b9-67df-ccd2-5ce46f264b5a@collabora.com>
On 2022/6/29 7:02, Dmitry Osipenko wrote:
> On 6/28/22 15:10, YueHaibing wrote:
>> WARNING: unmet direct dependencies detected for TEGRA20_APB_DMA
>> Depends on [n]: DMADEVICES [=n] && (ARCH_TEGRA [=y] || COMPILE_TEST [=n])
>> Selected by [y]:
>> - SOC_TEGRA_FUSE [=y] && ARCH_TEGRA [=y] && ARCH_TEGRA_2x_SOC [=y]
>>
>> TEGRA20_APB_DMA depends on DMADEVICES, so SOC_TEGRA_FUSE also should depends on it
>> before select it.
>>
>> Fixes: 19d41e5e9c68 ("soc/tegra: fuse: Add APB DMA dependency for Tegra20")
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>> ---
>> drivers/soc/tegra/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/soc/tegra/Kconfig b/drivers/soc/tegra/Kconfig
>> index 5725c8ef0406..2b6ba0f798fa 100644
>> --- a/drivers/soc/tegra/Kconfig
>> +++ b/drivers/soc/tegra/Kconfig
>> @@ -135,6 +135,7 @@ endif
>> config SOC_TEGRA_FUSE
>> def_bool y
>> depends on ARCH_TEGRA
>> + depends on DMADEVICES
>> select SOC_BUS
>> select TEGRA20_APB_DMA if ARCH_TEGRA_2x_SOC
>>
>
> Since it's a problem only for the Tegra20 config, shouldn't it be:
>
> - select TEGRA20_APB_DMA if ARCH_TEGRA_2x_SOC
> + select TEGRA20_APB_DMA if (ARCH_TEGRA_2x_SOC && DMADEVICES)
Indeed, will do this in v2.
>
> ?
>
prev parent reply other threads:[~2022-06-29 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:10 YueHaibing
2022-06-28 23:02 ` Dmitry Osipenko
2022-06-29 1:43 ` YueHaibing [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=83392db3-e8d1-e839-3cb6-e90e14044a56@huawei.com \
--to=yuehaibing@huawei.com \
--cc=digetx@gmail.com \
--cc=dmitry.osipenko@collabora.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®