From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753339AbcADKLe (ORCPT <rfc822;w@1wt.eu>);
	Mon, 4 Jan 2016 05:11:34 -0500
Received: from foss.arm.com ([217.140.101.70]:51754 "EHLO foss.arm.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753234AbcADKLc (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 4 Jan 2016 05:11:32 -0500
Date: Mon, 4 Jan 2016 10:11:24 +0000
From: Will Deacon <will.deacon@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Rongrong Zou <zourongrong@huawei.com>,
        Rongrong Zou <zourongrong@gmail.com>, minyard@acm.org,
        gregkh@linuxfoundation.org, catalin.marinas@arm.com,
        linuxarm@huawei.com, linux-kernel@vger.kernel.org,
        benh@kernel.crashing.org, lijianhua@huawei.com
Subject: Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced
Message-ID: <20160104101124.GA1616@arm.com>
References: <1451396032-23708-1-git-send-email-zourongrong@gmail.com>
 <1628979.qkJQGmVH0I@wuerfel>
 <5683A3B4.7040005@huawei.com>
 <23432380.Bk9bdl2Z0r@wuerfel>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <23432380.Bk9bdl2Z0r@wuerfel>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Dec 30, 2015 at 10:42:50AM +0100, Arnd Bergmann wrote:
> On Wednesday 30 December 2015 17:28:20 Rongrong Zou wrote:
> > >>
> > >
> > > config ARM64_INDIRECT_PIO
> > >       bool
> > >       help
> > >         Any driver that provides indirect ISA I/O port access should select
> > >         this symbol
> > 
> > 
> > >
> > > config HISILICON_HI123456_LPC
> > >       bool "Workaround for nonstandard ISA I/O space on Hisilicon Hi123456 SoC"
> > >       depends on ARCH_HISI || COMPILE_TEST
> > >       select ARM64_INDIRECT_PIO
> > >       help
> > >         ...
> > Can it be a submenu of "Platform selection--->Hisilicon SoC Family"?
> 
> The first should be in the main Kconfig file for arm64, the second one depends
> on where we put the respective code. I'd say both the Kconfig entry and the file
> can go into drivers/bus, but arch/arm64/kernel/ is also fine with me.

Unsurprisingly, I'd *much* prefer drivers/bus/ !

Will