Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1300612 > unrolled thread

Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced

Started byWill Deacon <will.deacon@arm.com>
First post2016-01-04 11:20 +0100
Last post2016-01-04 11:30 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced Will Deacon <will.deacon@arm.com> - 2016-01-04 11:20 +0100
    Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced Rongrong Zou <zourongrong@huawei.com> - 2016-01-04 11:30 +0100

#1300612 — Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced

FromWill Deacon <will.deacon@arm.com>
Date2016-01-04 11:20 +0100
SubjectRe: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced
Message-ID<qNap5-274-41@gated-at.bofh.it>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1300614

FromRongrong Zou <zourongrong@huawei.com>
Date2016-01-04 11:30 +0100
Message-ID<qNayK-2al-7@gated-at.bofh.it>
In reply to#1300612
在 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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web