From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the arm-soc tree with the arm-perf tree
Date: Mon, 23 Mar 2015 15:13:51 +0000 [thread overview]
Message-ID: <55102DAF.7050206@arm.com> (raw)
In-Reply-To: <CAM4voanC-ur=A-UJ+Jw4qECUOnd-gZ2V87794tEVWJOqaqDT+g@mail.gmail.com>
On 23/03/15 14:41, Abhilash Kesavan wrote:
> Hi Stephen,
>
> On Mon, Mar 23, 2015 at 6:03 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi all,
>>
>> Today's linux-next merge of the arm-soc tree got a conflict in
>> drivers/bus/Kconfig between commit c9966c98697a ("arm-cci: Split the
>> code for PMU vs driver support") from the arm-perf tree and commit
>> 13fbf3c8d0f7 ("drivers: bus: Sort Kconfig entries alphabetically") from
>> the arm-soc tree.
>>
>> I fixed it up (see below) and can carry the fix as necessary (no action
>> is required).
>
> Not sure if this has been reported elsewhere, but I am seeing core
> boot-up failures on the exynos5420 with next-20150323 due to this.
> Your conflict fix is missing the ARM_CCI symbol because of which the
> CCI does not get enabled.
>
> Suzuki, can you confirm ?
>
Yes, you are right. We need the config ARM_CCI even now, which enables
the building of the arm-cci.c.
Stephen,
We need the following fix on the linux-next.
Suzuki
diff --git a/drivers/bus/Kconfig b/drivers/bus/Kconfig
index f4213b1..e0eac5a 100644
--- a/drivers/bus/Kconfig
+++ b/drivers/bus/Kconfig
@@ -4,6 +4,9 @@
menu "Bus devices"
+config ARM_CCI
+ bool
+
config ARM_CCI400_PORT_CTRL
bool
depends on ARM && OF && CPU_V7
> Regards,
> Abhilash
>>
>> --
>> Cheers,
>> Stephen Rothwell sfr at canb.auug.org.au
>>
>> diff --cc drivers/bus/Kconfig
>> index 79e297b1f221,7e9c2674af81..000000000000
>> --- a/drivers/bus/Kconfig
>> +++ b/drivers/bus/Kconfig
>> @@@ -4,6 -4,21 +4,38 @@@
>>
>> menu "Bus devices"
>>
>> -config ARM_CCI
>> - bool "ARM CCI driver support"
>> ++config ARM_CCI400_PORT_CTRL
>> ++ bool
>> + depends on ARM && OF && CPU_V7
>> ++ select ARM_CCI400_COMMON
>> + help
>> - Driver supporting the CCI cache coherent interconnect for ARM
>> - platforms.
>> ++ Low level power management driver for CCI400 cache coherent
>> ++ interconnect for ARM platforms.
>> ++
>> ++config ARM_CCI400_PMU
>> ++ bool "ARM CCI400 PMU support"
>> ++ default y
>> ++ depends on ARM || ARM64
>> ++ depends on HW_PERF_EVENTS
>> ++ select ARM_CCI400_COMMON
>> ++ help
>> ++ Support for PMU events monitoring on the ARM CCI cache coherent
>> ++ interconnect.
>> ++
>> ++ If unsure, say Y
>> ++
>> ++config ARM_CCI400_COMMON
>> ++ bool
>> ++ select ARM_CCI
>> +
>> + config ARM_CCN
>> + bool "ARM CCN driver support"
>> + depends on ARM || ARM64
>> + depends on PERF_EVENTS
>> + help
>> + PMU (perf) driver supporting the ARM CCN (Cache Coherent Network)
>> + interconnect.
>> +
>> config BRCMSTB_GISB_ARB
>> bool "Broadcom STB GISB bus arbiter"
>> depends on ARM || MIPS
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
next prev parent reply other threads:[~2015-03-23 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 0:33 linux-next: manual merge of the arm-soc tree with the arm-perf tree Stephen Rothwell
2015-03-23 14:41 ` Abhilash Kesavan
2015-03-23 15:13 ` Suzuki K. Poulose [this message]
2015-03-23 21:16 ` Stephen Rothwell
2015-03-24 14:59 ` Suzuki K. Poulose
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 23:03 Stephen Rothwell
2024-01-03 17:30 ` Will Deacon
2024-01-03 17:38 ` Arnd Bergmann
2014-02-21 0:58 Stephen Rothwell
2014-02-21 1:02 ` Olof Johansson
2014-02-21 11:09 ` Will Deacon
2014-02-22 0:46 ` Olof Johansson
2014-02-21 1:02 ` Stephen Boyd
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=55102DAF.7050206@arm.com \
--to=suzuki.poulose@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).