From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756055AbaIIKZG (ORCPT ); Tue, 9 Sep 2014 06:25:06 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:50698 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752521AbaIIKZD (ORCPT ); Tue, 9 Sep 2014 06:25:03 -0400 From: Arnd Bergmann To: Murali Karicheri Cc: linux-arm-kernel@lists.infradead.org, Mark Rutland , devicetree@vger.kernel.org, Pawel Moll , Ian Campbell , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Santosh Shilimkar , Kumar Gala , Bjorn Helgaas Subject: Re: [PATCH] PCI: keystone: update to support multiple pci ports Date: Tue, 09 Sep 2014 12:24:48 +0200 Message-ID: <5974944.bS5MvrslRo@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <540DD0CF.4000501@ti.com> References: <1409938782-31460-1-git-send-email-m-karicheri2@ti.com> <5769746.NkKjYOOUiv@wuerfel> <540DD0CF.4000501@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:O+RBHPQo09WfapUxos2T9vvx90Qq0NNE+2eqBcoywl9 /OY80srntpxZBZMeFRo7ktgBTTrzqsZfeQPCDpZmvj9lqY8ET6 gzMsEumHbCtbipAMpuRsBvy/JRzRT2dw1nBo9ziHF+MnHUf/5y af2Q5cBIMyOMuMuBt6h2ab1n6ypae3ZTh4wqN35ypZPqjaLs0r PHMOTsLEhST1AqT83pK+7/J04xvqjq14LfZ/VaU9EaH3GytpkO vTWe0iXxtf4MgBE+pZpFRxzNBwukKIC8ofkX9oZF+IdJJ2sGJA fzaSoPciDfffAd1wK9lyeGussfZ7UAxHWtlEg1HCm4QVPAskU2 cdiUspYZD6HLE52u7y1Y= X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 08 September 2014 11:52:47 Murali Karicheri wrote: > On 09/05/2014 05:11 PM, Arnd Bergmann wrote: > > But the driver can only do root complex mode, and we would probably > > want a completely different driver if we were to start supporting > > endpoint mode. > > Good point! I will drop index#2 handling in the driver code and will > handle the same in boot loader. But I have a question though. The > original driver which is queued up for merge to v3.18 has index #2 for > this reg offset and is documented in the DT documentation as > > index 2 is the base address and length of PCI mode configuration > register. > index 3 is the base address and length of PCI device ID register. > > > Will this create any issue in terms of backward compatibility if I > remove it and move index3 to index2 and update the code for the same? I > assume since this patch also will likely be on the next branch soon, and > gets merged together with original driver to v3.18, this should be fine. > But for some reason, if this patch doesn't make to v3.18, then won't > this break the backward compatibility? > > I think the other option is document index2 as obsolete and update the > document and remove the code for handling it. Any suggestion? Since the driver is not merged into Linus' tree yet and (more importantly) has not been in a release yet, we can still fix it. Please just send a patch on top to remove it now, it's not too late yet. Arnd