All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Gerhard Bertelsmann <info@gerhard-bertelsmann.de>
Cc: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>,
	Pankajkumar Misra <pankaj.kumar@in.bosch.com>,
	linux-can@vger.kernel.org, linux-can-owner@vger.kernel.org
Subject: Re: CAN implementation on A20 Allwinner
Date: Thu, 27 Aug 2015 16:37:12 +0200	[thread overview]
Message-ID: <55DF2098.4020105@pengutronix.de> (raw)
In-Reply-To: <8a0d66b660360693b2b9b4ae7da78cd4@mail.rdts.de>

[-- Attachment #1: Type: text/plain, Size: 2060 bytes --]

On 08/27/2015 04:29 PM, Gerhard Bertelsmann wrote:
>>> Some regs also have a different address
>>
>> Which one? How may?
> 
> here a quick overview (not a complete list):
> 
>    original    address    Allwinner
> SJA1000_MOD    0x00   CAN_MOD_SEL    OK
> SJA1000_CMR    0x01   CAN_CMD_REG    OK
> SJA1000_SR     0x02   CAN_STA_REG    OK but 24 bit (more values)
> SJA1000_IR     0x03   CAN_INT_REG    OK
> SJA1000_IER    0x04   CAN_INTE_REG   OK
>                 0x05   CAN_BUS_TIME   NOK also 24 bit
> SJA1000_BTR0   0x06   CAN_TEWL       NOK CAN TX error warn limit reg
> SJA1000_BTR1   0x07   CAN_ERRC       NOK CAN error counter register
> SJA1000_OCR    0x08   CAN_RMCNT      NOK CAN receive message count reg
> 
> SJA1000_ALC    0x0B                  NOK
> SJA1000_ECC    0x0C                  NOK
> SJA1000_EWL    0x0D                  NOK
> SJA1000_RXERR  0x0E                  NOK
> SJA1000_TXERR  0x0F                  NOK
> SJA1000_ACCC0  0x10   CAN_AC0        OK  Reset mode: CAN_ACP_CODE but 32 
> bit
> SJA1000_ACCC1  0x11   CAN_AM0        NOK Reset mode: CAN_ACP_CODE 32 bit
> SJA1000_ACCC2  0x12   CAN_TRBUF2     NOK CAN TX/RX mbuffer 2 reg
> SJA1000_ACCC3  0x13   CAN_TRBUF3     NOK CAN TX/RX mbuffer 3 reg
> SJA1000_ACCM0  0x14   CAN_TRBUF4     NOK CAN TX/RX mbuffer 4 reg
> SJA1000_ACCM1  0x15   CAN_TRBUF5     NOK CAN TX/RX mbuffer 5 reg
> SJA1000_ACCM2  0x16   CAN_TRBUF6     NOK CAN TX/RX mbuffer 6 reg
> SJA1000_ACCM3  0x17   CAN_TRBUF7     NOK CAN TX/RX mbuffer 7 reg
> SJA1000_RMC    0x1D   CAN_TRBUF8     NOK CAN TX/RX mbuffer 8 reg
> SJA1000_RBSA   0x1E   CAN_TRBUF9     NOK CAN TX/RX mbuffer 9 reg
> 
> more differences than similarities ... A sja1000 module with "quirks" 
> makes
> no sense to me.

ACK

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2015-08-27 14:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  9:43 Why doesn't the socketcan prio qdisc work for first 10 can frames? Ruan TingQuan (ST-FIR/ENG1-Zhu)
2014-11-27 11:46 ` Oliver Hartkopp
2014-11-27 17:54   ` CAN implementation on A20 Allwinner Pankajkumar Misra (RBEI/EEA2)
2014-11-27 18:28     ` Uwe Bonnes
     [not found]       ` <58243.88.153.236.115.1417116776.squirrel@webmail.rdts.de>
2014-11-27 19:53         ` Gerhard Bertelsmann
2014-12-02 12:37           ` Marc Kleine-Budde
2015-08-27 13:04             ` Gerhard Bertelsmann
2015-08-27 13:23               ` Marc Kleine-Budde
2015-08-27 13:34                 ` Gerhard Bertelsmann
2015-08-27 13:49                   ` Marc Kleine-Budde
2015-08-27 14:29                     ` Gerhard Bertelsmann
2015-08-27 14:37                       ` Marc Kleine-Budde [this message]
2015-08-28  5:41                         ` Misra Pankaj Kumar (RBEI/EEA2)
2015-08-28  6:21                           ` Marc Kleine-Budde
2015-08-28  9:22                             ` Gerhard Bertelsmann
2015-08-28 10:11                               ` Marc Kleine-Budde

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=55DF2098.4020105@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=bon@elektron.ikp.physik.tu-darmstadt.de \
    --cc=info@gerhard-bertelsmann.de \
    --cc=linux-can-owner@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=pankaj.kumar@in.bosch.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.