From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-parisc@vger.kernel.org, Helge Deller <deller@gmx.de>,
jejb@parisc-linux.org,
Alexander Beregalov <a.beregalov@gmail.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: sti: don't select CONFIG_VT
Date: Fri, 05 May 2017 15:27:06 +0000 [thread overview]
Message-ID: <3242330.XRvUNh2arJ@amdc3058> (raw)
In-Reply-To: <20170428195151.57706-1-arnd@arndb.de>
On Friday, April 28, 2017 09:51:25 PM Arnd Bergmann wrote:
> While working on another build error, I ran into several variations of
> this dependency loop:
>
> subsection "Kconfig recursive dependency limitations"
> drivers/input/Kconfig:8: symbol INPUT is selected by VT
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/tty/Kconfig:12: symbol VT is selected by FB_STI
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/video/fbdev/Kconfig:677: symbol FB_STI depends on FB
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/video/fbdev/Kconfig:5: symbol FB is selected by DRM_KMS_FB_HELPER
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/gpu/drm/Kconfig:72: symbol DRM_KMS_FB_HELPER is selected by DRM_KMS_CMA_HELPER
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/gpu/drm/Kconfig:137: symbol DRM_KMS_CMA_HELPER is selected by DRM_HDLCD
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/gpu/drm/arm/Kconfig:6: symbol DRM_HDLCD depends on OF
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/of/Kconfig:4: symbol OF is selected by X86_INTEL_CE
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> arch/x86/Kconfig:523: symbol X86_INTEL_CE depends on X86_IO_APIC
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> arch/x86/Kconfig:1011: symbol X86_IO_APIC depends on X86_LOCAL_APIC
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> arch/x86/Kconfig:1005: symbol X86_LOCAL_APIC depends on X86_UP_APIC
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> arch/x86/Kconfig:980: symbol X86_UP_APIC depends on PCI_MSI
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/pci/Kconfig:11: symbol PCI_MSI is selected by AMD_IOMMU
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/iommu/Kconfig:106: symbol AMD_IOMMU depends on IOMMU_SUPPORT
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/iommu/Kconfig:5: symbol IOMMU_SUPPORT is selected by DRM_ETNAVIV
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/gpu/drm/etnaviv/Kconfig:2: symbol DRM_ETNAVIV depends on THERMAL
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/thermal/Kconfig:5: symbol THERMAL is selected by ACPI_VIDEO
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/acpi/Kconfig:183: symbol ACPI_VIDEO is selected by INPUT
>
> This doesn't currently show up as I fixed the 'THERMAL' part of it,
> but I noticed that the FB_STI dependency should not be there but
> was introduced by slightly incorrect bug-fix patch that tried to
> fix a link error.
>
> Instead of selecting 'VT' to make us enter the drivers/video/console
> directory at compile-time, it's sufficient to build the
> drivers/video/console/sticore.c file by adding its directory
> to when CONFIG_FB_STI is enabled. Alternatively, we could move the
> sticore code to another directory that is always built when we
> have at STI_CONSOLE or FB_STI enabled.
>
> Fixes: 17085a934592 ("parisc: stifb: should depend on STI_CONSOLE")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Patch queued for 4.12, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2017-05-05 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170428195120epcas2p2792c14bbbd4cf86be1b84c7f3d0f2040@epcas2p2.samsung.com>
2017-04-28 19:51 ` [PATCH] fbdev: sti: don't select CONFIG_VT Arnd Bergmann
2017-05-05 15:27 ` Bartlomiej Zolnierkiewicz [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=3242330.XRvUNh2arJ@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=a.beregalov@gmail.com \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.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).