Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754012AbaLMTsE (ORCPT ); Sat, 13 Dec 2014 14:48:04 -0500 Received: from mout.kundenserver.de ([212.227.17.10]:57550 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752813AbaLMTsB (ORCPT ); Sat, 13 Dec 2014 14:48:01 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Arend van Spriel , Mark Rutland , devicetree@vger.kernel.org, Florian Fainelli , Russell King , Scott Branden , Pawel Moll , Ian Campbell , Ray Jui , Christian Daudt , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Matt Porter , Grant Likely , Rob Herring , bcm-kernel-feedback-list@broadcom.com, Hauke Mehrtens , Kumar Gala , Bjorn Helgaas , Lucas Stach Subject: Re: [PATCH v2 1/4] pci: iProc: define Broadcom iProc PCIe binding Date: Sat, 13 Dec 2014 20:46:42 +0100 Message-ID: <3383252.Ad6Qf0H2fa@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <548C0F80.2090300@broadcom.com> References: <1418351817-14898-2-git-send-email-rjui@broadcom.com> <3907917.zNo7yttzkh@wuerfel> <548C0F80.2090300@broadcom.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:MFWNqZnnNvoeC7+rMvFz1P4WGgBo5W45FkTXtwu9g7jE6NV/CSS kse/rZ+bWs5uIfL2i93e3lRg5jIlIt5FPNkPR6faZIR/ZFezxA/bcO7CcyWPCWhs8j/ZQaT t/PBTjeUxdOSW4BLCaT6CDCHhwaA770airpIK669B1wnxLksy1GpZbD4dRM0RNewX0zg0b4 pib2TN2/WczdvDiRGEaAQ== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 13 December 2014 11:05:52 Arend van Spriel wrote: > > Makes sense. I think that is what Hauke meant by "adding > additional support for registering to bcma". So the discovery info is a > piece of read-only memory in the chip. Its address is stored in the > chipcommon core register space. BCMA parses that memory blob resulting > in a list of cores which register address info. We could add DT support > in BCMA matching the compatible string and register a core for it. Ah, interesting idea. That would mirror what we do for drivers/amba, I like the idea. > However, apart from the discovery info a "discoverable ARM AXI" chip has > a register space per core that provides common procedures like > enable/disable, reset, core status, which are implemented in BCMA. I am > not seeing that register space in the DT examples so I guess this IP > block is not there for iProc chips. I wouldn't draw conclusions from the absence of some node. Maybe these registers are present but just not used by the original BSP. Arnd -- 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/