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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Dec 2015 10:42:50 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Rongrong Zou <zourongrong@...wei.com>
Cc:	Rongrong Zou <zourongrong@...il.com>, minyard@....org,
	gregkh@...uxfoundation.org, catalin.marinas@....com,
	will.deacon@....com, linuxarm@...wei.com,
	linux-kernel@...r.kernel.org, benh@...nel.crashing.org,
	lijianhua@...wei.com
Subject: Re: [PATCH v1 1/3] ARM64 LPC: indirect ISA PORT IO introduced

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
--
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/