[lkml]   [2011]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] drivers: brcmaxi: provide amba axi functionality in separate module
    On Sat, 23 Apr 2011 14:33:21 +0200, Jonas Gorski <>  

    > On 21 April 2011 16:38, Arend van Spriel <> wrote:
    >> Would it be possible to make chipcommon driver optional (not doing the
    >> initialization)?
    > This would need to be done on a per-device/bus basis, at least for
    > embedded. Consider the following setup (which is quite common for dual
    > band routers):
    > BCM4718 (bus A)
    +- MIPS74k
    > +- Common Core <- provides flash write access, GPIOs, watchdog, ...
    > +- 802.11 Core <- for 2.4Ghz wifi
    > +- PCIe Core
    > + BCM43224 (bus B)
    > +- Common Core
    > +- 802.11 Core <- for 5Ghz wifi
    > (I omitted any cores not relevant for the example)

    The MIPS may be relevant as well ;-)

    In the example above I would expect two axi bus driver instances for bus A
    and bus B.

    > So eventually you want to able to drive both 802.11 cores, but can't
    > exclusively claim both common cores.

    I would expect to be probed twice. One call for 2.4GHz 802.11 core
    referencing to bus A and one call for 5GHz 802.11 core referencing to bus

    Regarding chipcommon I agree that it requires one init sequence per
    device. I would just like to have the option to provide a custom
    initialization function for chip common (and possibly pcie) somehow.

    Gr. AvS
    "The world is indeed comic, but the joke is on mankind." — H.P. Lovecraft

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2011-04-23 17:11    [W:0.021 / U:3.352 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site