Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752121Ab1DNL2N (ORCPT ); Thu, 14 Apr 2011 07:28:13 -0400 Received: from mail-qy0-f181.google.com ([209.85.216.181]:58461 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751192Ab1DNL2L convert rfc822-to-8bit (ORCPT ); Thu, 14 Apr 2011 07:28:11 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=QDPYziV/vdDNnuHsNt2H26AHrADa66sjnpK3WGUkbro8OBhmXBL3ifP2C2zOPhhwQg bVj9oGPQ9oweCGCIqMTwMqnN+DLilGwdjVZ97zvbZ6+iNVlyLSzWFqA1DKrRx+yiELdS F2wR5sa+jryL7aYTGGKORptqVhxufXnGeqMpI= MIME-Version: 1.0 Date: Thu, 14 Apr 2011 13:28:10 +0200 Message-ID: Subject: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus? From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, linux-arm-kernel@lists.infradead.org, George Kashperko , Arend van Spriel , Jonas Gorski , Russell King , Arnd Bergmann Cc: b43-dev@lists.infradead.org, Greg KH , Andy Botting , Larry Finger Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2048 Lines: 46 Hello, We have slightly improved our knowledge of new Broadcom's bus. It appears Broadcom took standard AMBA bus and put on it two cores for every device: 1) First core from each pair is real AMBA device, it has CID and PID. Broadcom called it wrapper, it is used to control second core (enabling second, disabling second, resetting second, setting flags of second). 2) Second core from each pair is Broadcom specific device. It can *not* be treated as standard AMBA core - attempting to read it's CID on PID leads to machine hang. Instead it is identified by MANUF, ID, REV and CLASS. Example can be 80211 core. One of the idea is to integrate with current AMBA driver: 1) First driver read info about all cores in Broadcom specific way. It registers all *wrapper* (AMBA type) cores as amba_device(s). 2) Second driver registers for cores with PID 0x103BB369 (Broadcom specific I believe). It receives wrappers (from AMBA bus) and exposes wrapper-related Broadcom specific core in the system. Problem: how to expose Broadcom specific cores in the system? Remember we can not use amba_device, because Broadcom specific cores are programmed and identified differently. Could we register some virtual bcm_amba bus in the system and register Broadcom specific cores with it? Or is there something better for this case? In summary everything I need is to make driver (for example b43) able to register for Broadcom specific core with Broadcom specific identifiers. For example: static const struct axi_device_id b43_axi_tbl[] = { AXI_CORE(AXI_MANUF_BCM, AXI_CORE_80211, 0x17, AXI_ANY_CLASS), AXI_CORETABLE_END }; MODULE_DEVICE_TABLE(axi, b43_axi_tbl); We have problems deciding architecture, the whole proposed layout is not approved as final yet. Right now I try to check possibilities. -- Rafał -- 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/