linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alex Bounine <alex.bou9@gmail.com>
To: Christoph Hellwig <hch@infradead.org>, Alexei Colin <acolin@isi.edu>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Russell King <linux@armlinux.org.uk>,
	John Paul Walters <jwalters@isi.edu>,
	x86@kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-mips@linux-mips.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 6/6] arm64: enable RapidIO menu in Kconfig
Date: Wed, 1 Aug 2018 09:15:57 -0400	[thread overview]
Message-ID: <fad8661c-cd8c-3a9c-ca03-5d2f63893a24@gmail.com> (raw)
In-Reply-To: <20180801095404.GA17585@infradead.org>

On 2018-08-01 05:54 AM, Christoph Hellwig wrote:
> On Tue, Jul 31, 2018 at 10:29:54AM -0400, Alexei Colin wrote:
>> Platforms with a PCI bus will be offered the RapidIO menu since they may
>> be want support for a RapidIO PCI device. Platforms without a PCI bus
>> that might include a RapidIO IP block will need to "select HAS_RAPIDIO"
>> in the platform-/machine-specific "config ARCH_*" Kconfig entry.
>>
>> Tested that kernel builds for arm64 with RapidIO subsystem and
>> switch drivers enabled, also that the modules load successfully
>> on a custom Aarch64 Qemu model.
> 
> As said before, please include it from drivers/Kconfig so that _all_
> architectures supporting PCI (or other Rapidio attachements) get it
> and not some arbitrary selection of architectures.
> 
As it was replied earlier this is not a random selection of 
architectures but only ones that implement support for RapidIO as system 
bus. If other architectures choose to adopt RapidIO we will include them 
as well.

On some platforms RapidIO can be the only system bus available replacing 
PCI/PCIe or RapidIO can coexist with PCIe.

As it is done now, RapidIO is configured in "Bus Options" (x86/PPC) or 
"Bus Support" (ARMs) sub-menu and from system configuration option it 
should be kept this way.

Current location of RAPIDIO configuration option is familiar to users of 
PowerPC and x86 platforms, and is similarly available in some ARM 
manufacturers kernel code trees.

drivers/Kconfig will be used for configuring drivers for peripheral 
RapidIO devices if/when such device drivers will be published.

  reply	other threads:[~2018-08-01 13:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 14:29 [RESEND PATCH 0/6] rapidio: move Kconfig menu definition to subsystem Alexei Colin
2018-07-31 14:29 ` [RESEND PATCH 1/6] rapidio: define top Kconfig menu in driver subtree Alexei Colin
2018-07-31 15:09   ` Alexander Sverdlin
2018-07-31 15:29   ` Russell King - ARM Linux
2018-07-31 14:29 ` [RESEND PATCH 2/6] x86: factor out RapidIO Kconfig menu Alexei Colin
2018-07-31 14:29 ` [RESEND PATCH 3/6] powerpc: factor out RapidIO Kconfig menu entry Alexei Colin
2018-07-31 14:29 ` [RESEND PATCH 4/6] mips: factor out RapidIO Kconfig entry Alexei Colin
2018-07-31 14:29 ` [RESEND PATCH 5/6] arm: enable RapidIO menu in Kconfig Alexei Colin
2018-07-31 15:36   ` Russell King - ARM Linux
2018-07-31 14:29 ` [RESEND PATCH 6/6] arm64: " Alexei Colin
2018-08-01  9:54   ` Christoph Hellwig
2018-08-01 13:15     ` Alex Bounine [this message]
2018-08-02  8:57       ` Geert Uytterhoeven
2018-08-02 13:45         ` Alexei Colin
2018-08-02 13:54           ` Christoph Hellwig
2018-08-02 14:00             ` Alexei Colin
2018-08-02 14:16               ` Alex Bounine
2018-07-31 15:12 ` [RESEND PATCH 0/6] rapidio: move Kconfig menu definition to subsystem Alex Bounine
2018-07-31 15:59 ` Russell King - ARM Linux
2018-07-31 18:21   ` Alex Bounine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fad8661c-cd8c-3a9c-ca03-5d2f63893a24@gmail.com \
    --to=alex.bou9@gmail.com \
    --cc=acolin@isi.edu \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=hch@infradead.org \
    --cc=jwalters@isi.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).