linux-kernel - Re: [RFC PATCH 1/2] PCI: designware: Add ARM64 PCI support

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]

Message-ID: <CAL_JsqJ5=7bvxQZhbn4unDH0wTB=qn4nEnqGCnskvOmRhJ8JQw@mail.gmail.com>
Date:	Tue, 22 Apr 2014 10:39:29 -0500
From:	Rob Herring <robherring2@...il.com>
To:	Jingoo Han <jg1.han@...sung.com>
Cc:	Arnd Bergmann <arnd@...db.de>, Liviu Dudau <Liviu.Dudau@....com>,
	linux-pci <linux-pci@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kukjin Kim <kgene.kim@...sung.com>,
	Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
	Mohit KUMAR DCG <Mohit.KUMAR@...com>,
	Pratyush Anand <pratyush.anand@...com>,
	Marek Vasut <marex@...x.de>,
	Richard Zhu <r65037@...escale.com>,
	Kishon Vijay Abraham I <kishon@...com>,
	Byungho An <bh74.an@...sung.com>
Subject: Re: [RFC PATCH 1/2] PCI: designware: Add ARM64 PCI support

On Mon, Apr 21, 2014 at 4:58 AM, Jingoo Han <jg1.han@...sung.com> wrote:
> On Monday, April 21, 2014 10:54 AM, Jingoo Han wrote:
>> On Thursday, April 17, 2014 3:26 AM, Arnd Bergmann wrote:
>> > On Wednesday 16 April 2014 17:57:24 Liviu Dudau wrote:
>> > > Jingoo,
>> > >
>> > > Thanks for taking a stab at trying to convert a host bridge
>> > > driver to use the new generic host bridge code.
>> > >
>> > > I do however have concerns on the direction you took. You have split
>> > > your driver in two, depending on whether it was CONFIG_ARM or CONFIG_ARM64,
>> > > even if (with my series) it should be no reason why the host bridge
>> > > driver should not work on other architectures as well once they are
>> > > converted.
>> >
>> > Right.
>> >
>> > > Also, some of the functions that you use have identical names but different
>> > > signatures depending on what arch you have selected. This is really bad
>> > > in my books!
>
> [.....]
>
>> > > What about creating functions that use my series directly if CONFIG_ARM64 is
>> > > defined (or any CONFIG_ you want to create for your driver that you select
>> > > from CONFIG_ARM64) and otherwise implement the CONFIG_ARM version? That
>> > > way your driver will call only one API without any #ifdef and when arm code
>> > > gets converted you drop your adaptation functions. Or (better yet), have a
>> > > stab at converting bios32 (Rob Herring has already provided some hints on
>> > > how to do it for arch/arm).
>>
>> To: Liviu Dudau
>>
>> Sorry, but I will not implement this.

Then you will not get what you want upstream.

>> At first, you had to think the compatibility with ARM32 PCIe.
>> Why do you want other engineers to take this load?

That is how the process works.

> (+cc Rob Herring)
>
> Um, I am looking at Rob Herring's patchset for Versatile PCI. [1]
> Then, do you mean the following?
>
> 1. Add Rob Herring's patch converting bios32. [2]

I would expect all or most of this patch to go away in Liviu's next
version. It does at least show we don't have to fix all of ARM PCI
support to use of_create_pci_host_bridge on ARM.

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