linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zajec5@gmail.com (Rafał Miłecki)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH] axi: add AXI bus driver
Date: Wed, 13 Apr 2011 21:50:36 +0200	[thread overview]
Message-ID: <BANLkTik6JZ-n3sVjCFK_x1yNRH3_o3_6rg@mail.gmail.com> (raw)
In-Reply-To: <op.vtvalzu33ri7v4@arend-laptop>

2011/4/13 Arend van Spriel <arend@broadcom.com>:
> On Tue, 12 Apr 2011 22:44:01 +0200, Rafa? Mi?ecki <zajec5@gmail.com> wrote:
>
>> 2011/4/12 George Kashperko <george@znau.edu.ua>:
>>>>
>>>> 2011/4/12 Rafa? Mi?ecki <zajec5@gmail.com>:
>>>> That way I see really low (or not at all) relation between out
>>>> (not)Broadcom bus and present AMBA bus.
>>>>
>>> Agree.
>>
>> Ehh, sounds like one more renaming to functions, defines, prefixes.
>>
>> Let's wait for Arend comments, he was the one voting for not-bcm-specific
>> name.
>>
>
> Hi Rafa?,
>
> Still think its better to stick with a generic name even if currently you
> only come across this in Broadcom chips right now. I do agree that the term
> 'axi' is implying something else than what this bus driver is providing. The
> name 'axi-dmp' I gave earlier may be more to the point.
>
> I also looked at the amba driver after receiving comments on the brcmaxi
> library module (this is what Hauke Mehrtens referred to) and came to similar
> conclusion as you did. It does however support PM properly so you may want
> to get inspiration in that area. I also noticed a reference to AMBA term APB
> which is a different bus in the AMBA family. AXI was introduced later as
> higher performance bus (in AMBA rev3 if I remember correctly).

I don't focus on PM yet, do not consider it a problem, it just needs some time.

Note for not involved: AMBA is family with few buses/interfaces
possible: AXI, AHB, ASB, APB, ATB [1].

So what are you saying is that drivers/amba/ is for AMBA APB? OK, I
can accept such a explanation and it makes me even more sure we need
another AMBA driver (this time: AMBA AXI).

The left question is: how much of the implemented code is AMBA AXI
specific and how much is Broadcom specific?
1) Does AMBA AXI identify cores by manuf, id, rev and class? Is this
really AMBA AXI specific and a evolution from simple "id" in AMBA APB?
2) Is this standard for AMBA AXI to keep list of available cores in
some specific memory (is this always EPROM like in case of Bcm?)?
3) Does every AMBA AXI device need enabling/disabling/resetting
routine we implemented? Is that really Bcm independent?

This is mostly what I already asked, but didn't get answer. Please,
explain to us what is AMBA AXI specific and what is Broadcom specific.

[1] http://en.wikipedia.org/wiki/Advanced_Microcontroller_Bus_Architecture

-- 
Rafa?

  reply	other threads:[~2011-04-13 19:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 23:57 [RFC][PATCH] axi: add AXI bus driver Rafał Miłecki
2011-04-11 23:22 ` Rafał Miłecki
2011-04-11 23:35 ` Greg KH
2011-04-12 13:04 ` Rafał Miłecki
2011-04-12 13:18   ` Arend van Spriel
2011-04-12 13:21     ` Rafał Miłecki
2011-04-12 13:27       ` Arend van Spriel
2011-04-12 13:36 ` Felipe Balbi
2011-04-12 18:47   ` George Kashperko
2011-04-12 18:59     ` Rafał Miłecki
2011-04-12 19:12       ` George Kashperko
2011-04-12 19:27         ` Rafał Miłecki
2011-04-12 19:34           ` George Kashperko
2011-04-12 19:46             ` Rafał Miłecki
2011-04-12 20:07               ` George Kashperko
2011-04-12 19:47           ` Hauke Mehrtens
2011-04-12 19:58             ` Rafał Miłecki
2011-04-12 20:13               ` Rafał Miłecki
2011-04-12 20:35                 ` George Kashperko
2011-04-12 20:44                   ` Rafał Miłecki
2011-04-12 20:57                     ` George Kashperko
2011-04-12 21:51                       ` SDHCI pre-rootfs kernel oops problem...? Nick Pelling
2011-04-13  8:16                     ` [RFC][PATCH] axi: add AXI bus driver Arend van Spriel
2011-04-13 19:50                       ` Rafał Miłecki [this message]
2011-04-13 20:23                         ` George Kashperko
2011-04-13 21:05                           ` Rafał Miłecki
2011-04-13 21:58                             ` Rafał Miłecki
2011-04-13 23:07                               ` Rafał Miłecki
2011-04-13 23:31                           ` Rafał Miłecki
2011-04-13 20:49                         ` Nick Bowler
2011-04-12 20:23             ` George Kashperko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BANLkTik6JZ-n3sVjCFK_x1yNRH3_o3_6rg@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).