linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Abhilash Kesavan <kesavan.abhilash@gmail.com>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Will Deacon <Will.Deacon@arm.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: linux-next: manual merge of the arm-soc tree with the arm-perf tree
Date: Tue, 24 Mar 2015 14:59:02 +0000	[thread overview]
Message-ID: <55117BB6.9050704@arm.com> (raw)
In-Reply-To: <20150324081610.52b1e92d@canb.auug.org.au>

On 23/03/15 21:16, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 23 Mar 2015 15:13:51 +0000 "Suzuki K. Poulose" <Suzuki.Poulose@arm.com> wrote:
>>
>> On 23/03/15 14:41, Abhilash Kesavan wrote:
>>>
>>> On Mon, Mar 23, 2015 at 6:03 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>>
>>>> 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.
>
> Oops, sorry about that.  I have fixed up the merge resolution for today
> so that file starts like this:
>
> #
> # Bus Devices
> #
>
> menu "Bus devices"
>
> config ARM_CCI
> 	bool
>
> config ARM_CCI400_COMMON
> 	bool
> 	select ARM_CCI
>
> 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_PORT_CTRL
> 	bool
> 	depends on ARM && OF && CPU_V7
> 	select ARM_CCI400_COMMON
> 	help
> 	  Low level power management driver for CCI400 cache coherent
> 	  interconnect for ARM platforms.

Looks good.

Thanks

Suzuki

  reply	other threads:[~2015-03-24 14:59 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
2015-03-23 21:16     ` Stephen Rothwell
2015-03-24 14:59       ` Suzuki K. Poulose [this message]
  -- 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=55117BB6.9050704@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=kesavan.abhilash@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    /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).