From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755357AbbIWUpu (ORCPT ); Wed, 23 Sep 2015 16:45:50 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:60364 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753386AbbIWUps (ORCPT ); Wed, 23 Sep 2015 16:45:48 -0400 From: Arnd Bergmann To: Will Deacon Cc: "linux-arm-kernel@lists.infradead.org" , David Daney , Mark Rutland , "devicetree@vger.kernel.org" , Pawel Moll , Ian Campbell , Marc Zyngier , "linux-pci@vger.kernel.org" , David Daney , "linux-kernel@vger.kernel.org" , Rob Herring , David Daney , Kumar Gala , Bjorn Helgaas Subject: Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Date: Wed, 23 Sep 2015 22:45:28 +0200 Message-ID: <2795004.Hn5xt30nZN@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1707525.QvfFzUYq4E@wuerfel> References: <1442527332-1174-1-git-send-email-ddaney.cavm@gmail.com> <20150923193545.GZ7356@arm.com> <1707525.QvfFzUYq4E@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:ztZ8ISASIW2onNYBMdRvf1myF38twJUC/lYvkkzv0PiwQ+H2GU0 S0mvwvLDvHI+ra7UzYYCaZUocX5wNPHN0FdRVgGETQdzcwsk/o3HAEaj/6cueYE14zY6K+2 ZXNhyMZooiZWk+EU+iXo2Sz3FWr5A0gN3pcfFMrGWQwcPH9NIURHoIEc2RlG67paXS8oB7F qxXxKGV5hE4Hm4l9105OQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:hxygFVHCacs=:vjJSrxDk24l1NovD3cwF5y u7NqtjrtQRRc7KX76lh3mtqny3NMgI7es327/KI5Jj7zkCOzUF/DmPVig4UUf44aUAMBRaHOd ZneP1nMP2jaElziiCO3k2x15Kp6jdyeQa0LXeqNixC+z7Po94/AWrwzJTHEXCyw83zLWp44sN A4HmHYNeApcosETRIhOkYmeBWJyHohyHlwQqNpk6g/XoGt1YB2E825GhMK2ViodQqQo8Q0tPg reNcMIfh40NAbLV7iHm0wUt0XC+gcl50xyT5QJgeRn2uu8EMOEtyYYECqzoNdOEWQEyqVabpe k6DL0LyszsRHP6E2kZuBYjYYSYKR5xkqvCXksELRg6WYn2JlICOAuKoVGR4GmfJWdmXY6yoZR XZ5YwP6PqeTITVdZah5LCRr1MmKBWM8OXoA4EpIb6Dt3pZTpQ3kSnfrWC07QcNHNRK4Ynj3HH roHYbC+RQ0CiepyWTtzNemUcW4Rk9I2mAxdd/fa+Q2uxHWrk1szW02gILk4nf/8XGVnDDoyiO ZaZrnskahHY+6ax9pLWoL8hETyXp92RT03jHkt9H6PtLKxuV1m1QSEWaiDlJ1iYHyLsn/9/ot 32RkIfqQxCu8peo3bEUyj6Z8/9xTwu6i1Z2DOQr9zIa4p/eMlo53SQ+mC3e2J0qz/KhxT+7P8 I5u+ViZU9Mu1Sl34lC82iYgL8cv0PxZVwJWI2IYkvg7bSJWjjH/OWdyg/JxyGioimTu/eHGlc pUUXFc7Gg6Hk/9zK Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 23 September 2015 21:39:27 Arnd Bergmann wrote: > On Wednesday 23 September 2015 20:35:45 Will Deacon wrote: > > > > From what Lorenzo was saying, ACPI shares the interpretation that David is > > implementing here and, given that the DT version seems to be subjective, > > aligning this reg property with MMCFG seems to make sense. > > We should then make it very clear in the binding that the driver > is not allowed to actually map the registers for the buses outside > of the bus-range, as that is highly unusual. One more point here: I think ACPI does something different here, it lists the base address of mmconfig space of the the PCI domain that the host bridge belongs to. In contrast, in DT the 'reg' property is defined as the registers belonging to the host bridge itself, and the DT does not say anything about domains at all (aside from the linux,pci-domain property that is not mandatory and a Linux-specific extension). Arnd