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 S1754530AbbL3JnR (ORCPT <rfc822;w@1wt.eu>);
	Wed, 30 Dec 2015 04:43:17 -0500
Received: from mout.kundenserver.de ([217.72.192.75]:62913 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754498AbbL3JnO (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 30 Dec 2015 04:43:14 -0500
From: Arnd Bergmann <arnd@arndb.de>
To: Rongrong Zou <zourongrong@huawei.com>
Cc: Rongrong Zou <zourongrong@gmail.com>, minyard@acm.org,
        gregkh@linuxfoundation.org, catalin.marinas@arm.com,
        will.deacon@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
Date: Wed, 30 Dec 2015 10:42:50 +0100
Message-ID: <23432380.Bk9bdl2Z0r@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <5683A3B4.7040005@huawei.com>
References: <1451396032-23708-1-git-send-email-zourongrong@gmail.com> <1628979.qkJQGmVH0I@wuerfel> <5683A3B4.7040005@huawei.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:BL32tSmQt7xMcSuunlHg9DzD/UjPFBTTgNmNgvqQW2mJSkblCFe
 j+P7a29tMr0Fje5NJ8n35HWmwGFQgb9ir+vVa+mvlmePVG6n+10ZHJy0UYK5b3UfGIg3oBN
 RRBwDwRDp1wb0zxTJRFgilndDHqrdyzXiOxympnhGL1svXRExD9/Sv/6f1p1CzIPZ++Tzjc
 xtErYwXfDXqpOGrqIgH1g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:xzrDqeJ7Sxk=:+IjaxSMiovWtBiQErKfUzK
 rmVttF2Xiy6OGzz/ZeYwZhvAlxumh6eV24u2j/3s41l3AKIDCnTktKDStmA8otPie/7biZi/y
 gxgrRhFRE5L1SOl1VLCULfL9Jdx40f2CRDc3n+dPye8Gz5H9iIP9HjQO+HS2B7e7nf1Ee/gZe
 2NPY9B/41Cg3m566iUjT/uEwb2b7FKRtD63J21fgugUT6Tdt/Sn//aDSYOLWgmLfZTuMSm0mK
 6VKS/pSBc3G0wNwJdLQebzFk2bmHsWFvIqd3yzfp1iyVPXOvvyY3/co4P8gPvifaK8SB9O/aq
 cBmrFwx1MKED+tJdkm1yC1FbVYW1RmLE90icu0JjloCieFerGZD7EH1nbfps5cdGhgcJYcEI+
 +evZFo5AKeKO8o7Ebc5mjego8Lbuqg1M/qkgMYDWVTDYdhFxqHi792HvY5IDGONuhO2MqHdKG
 mis+D/boRygVWTtFQhgWtzZdqYlWdw0CU7dzn6/XAt2/ez4rtQJzi/tkt+wPykPQo2vEeGGZw
 s1YRJeUMAWUTQy3itbWglrGdGe/lahF3oRcWfNk8rRLx71jvetb4+ox3pO0zBKcK/8BgVuHC2
 raMChIS1CmJOAFMyo3fpEuq6CNMQz+M9rFemIKyP2/N3LT7pz1IS/rHyC67rmOl6KdqmH/10z
 x6lXAiyOhk0QpJMTSFNYcGwueVlOIJpZaKz6bgFk57X6m30a2Ch6LGhV01/ssOrNI6BbMqD8a
 h9vQlQc1GKdo+xdm
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.

	Arnd