MIME-Version: 1.0
In-Reply-To: <20141111182418.GA5507@red-moon>
References: <1415702040-2790-1-git-send-email-ming.lei@canonical.com>
	<20141111122901.GA4419@red-moon>
	<CACVXFVNAc9axtESmo1zGZ3GMquTzjzWR3jx-b3tbhhLfQDDRcg@mail.gmail.com>
	<20141111182418.GA5507@red-moon>
Date: Wed, 12 Nov 2014 10:12:12 +0800
Message-ID: <CACVXFVPzo2qNGa5DWESS3TXor=u82_SxHb+xzrBCRXtcQxq4Cg@mail.gmail.com>
Subject: Re: [PATCH] pci: generic host: make it more generic
From: Ming Lei <ming.lei@canonical.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, Will Deacon <Will.Deacon@arm.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        alvise rigo <a.rigo@virtualopensystems.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org

On Wed, Nov 12, 2014 at 2:24 AM, Lorenzo Pieralisi
<lorenzo.pieralisi@arm.com> wrote:
> On Tue, Nov 11, 2014 at 02:02:20PM +0000, Ming Lei wrote:
>
> [...]
>
>> > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/296535.html
>> >
>> > Patch above is already queued and applies most of the changes you have posted
>> > above.
>>
>> I should have looked at list first before writing the patch, :-(
>>
>> Could you make it more generic so that other ARCHs(at least ARM64)
>> can benefit from it too?
>
> That's our current goal, we are carrying out clean-ups to remove arch
> dependency and move code to the generic layer PCI layer.

OK, I am glad to test them after you post them out.

At least, the 'struct gen_pci' pointer can be put in driver data
of the platform_device now, which may remove dependency on
pci_sysdata in this driver.  But ARCH's pcibios code still may
access 'pci_sysdata', do you have patches or solution to handle
this issue?

Do you think it is doable to introduce a option(from module
parameter, or device tree, ...) to let the driver and PCI core
ignore/bypass all pcibios handling for the generic bus?  If that
is OK, it can provide an approach to reach the goal a bit easy.
In reality, generic host controller should be only used by VM,
and VM's firmware shouldn't be very complicated and I think
the option can meet most of demands.

Thanks,
Ming Lei
--
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/