[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <568A4900.2030300@huawei.com>
Date: Mon, 4 Jan 2016 18:27:12 +0800
From: Rongrong Zou <zourongrong@...wei.com>
To: Will Deacon <will.deacon@....com>, Arnd Bergmann <arnd@...db.de>
CC: Rongrong Zou <zourongrong@...il.com>, <minyard@....org>,
<gregkh@...uxfoundation.org>, <catalin.marinas@....com>,
<linuxarm@...wei.com>, <linux-kernel@...r.kernel.org>,
<benh@...nel.crashing.org>, <lijianhua@...wei.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced
在 2016/1/4 18:11, Will Deacon 写道:
> 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/ !
I'll move it to drivers/bus on next version of patch, thanks!
>
> Will
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists