From: schindele@nentec.de (Juergen Schindele)
To: linux-arm-kernel@lists.infradead.org
Subject: IXP425: help on HSS channelized service
Date: Tue, 24 Nov 2009 17:22:43 +0200 [thread overview]
Message-ID: <200911241622.43464.schindele@nentec.de> (raw)
In-Reply-To: <4B0BDFC1.7010506@kaskonetworks.it>
Am Dienstag, 24. November 2009 schrieb Davide Di Gesualdo:
> Hi all,
Dear Davide,
i am using ixp4xx-hss for an HDLC.X21 frontend in packetized mode
with all timeslots from kernel version 2.6.27.36
To receive correctly i had to modify the parameters
in "hss_config_set_pcr" function. I compared to intel software stack
for IXP425 which was already working for us.
in function static void hss_config_set_pcr(struct port *port)
....
- msg.data32 = PCR_FRM_SYNC_OUTPUT_RISING | PCR_MSB_ENDIAN |
- PCR_TX_DATA_ENABLE;
+ msg.data32 = PCR_FRM_SYNC_ACTIVE_HIGH | PCR_MSB_ENDIAN |
+ PCR_TX_DATA_ENABLE | PCR_FCLK_EDGE_RISING | PCR_FRM_PULSE_DISABLED;
....
Nevertheless i am receiving correct data but packet len is always zero!
Have you already encountered this ???
Bye
> I'm writing a kernel module for a HSS channelized service on IXP425
> processor, based on ixp4xx_hss. I'm developing on a IXDPG425 Intel
> board, and the HSS bus is attached to four Si3210 ProSLIC chips.
> The purpose of this module is to read/write from/to HSS 8-byte buffers
> in raw mode (no particular alignment is required). In write direction,
> everything seems ok: if I write a buffer like
> char buf[] = {0xcb, 0xcb, 0xcb, 0xcb, 0xcb, 0xcb, 0xcb, 0xcb};
> on a fixed timeslot and then read the TXD pin signal with a scope, I can
> see the correct waveform at the correct place; I've also tried to write
> a tone with a fixed freqeuncy, and I've listened it correctly.
> The problem comes with read direction: I've tried to make a loopback by
> copying the rxbuffer in the txbuffer, but I can't hear my voice back
> (instead I hear something like a continous buzz). I'm quite sure I read
> the rxbuffer in the correct way (I do the same when I write txbuffer,
> which works properly!). This is the ISR for HSS read-complete interrupt:
--------------------------------------------------------------
J?rgen Schindele
Software-Entwicklung
NENTEC Netzwerktechnologie GmbH
Greschbachstr. 12
76229 Karlsruhe
Deutschland
Telefon: +49 721 94249-51
Telefax: +49 721 94249-10
E-Mail: schindele at nentec.de
WEB: www.nentec.de
Gesch?ftsf?hrung: Klaus Becker, Roland Knapp
Sitz der Gesellschaft: Karlsruhe
Handelsregister: Amtsgericht Mannheim HRB 107658
--------------------------------------------------------------
next prev parent reply other threads:[~2009-11-24 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 13:29 IXP425: help on HSS channelized service Davide Di Gesualdo
2009-11-24 15:22 ` Juergen Schindele [this message]
2009-11-25 0:07 ` Krzysztof Halasa
2009-11-25 12:52 ` Davide Di Gesualdo
2009-11-24 23:45 ` Krzysztof Halasa
2009-11-26 14:43 ` Juergen Schindele
2009-11-26 14:49 ` Russell King - ARM Linux
2009-11-26 15:44 ` Juergen Schindele
2009-11-26 15:51 ` Russell King - ARM Linux
2009-11-26 19:03 ` Krzysztof Halasa
2009-11-26 19:39 ` Krzysztof Halasa
2009-11-27 8:21 ` Juergen Schindele
2009-11-27 23:55 ` Krzysztof Halasa
2009-11-30 8:18 ` Juergen Schindele
-- strict thread matches above, loose matches on Subject: below --
2009-11-25 13:34 Davide Di Gesualdo
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=200911241622.43464.schindele@nentec.de \
--to=schindele@nentec.de \
--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).