From: "Søren holm" <sgh@sgh.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: Re: Hardware flowcontrol on XR17D154
Date: Tue, 30 Aug 2011 13:27:04 +0200 [thread overview]
Message-ID: <201108301327.04542.sgh@sgh.dk> (raw)
In-Reply-To: <20110830113433.618b2486@lxorguk.ukuu.org.uk>
Tirsdag den 30. august 2011 12:34:33 skrev Alan Cox:
>
> Can you explain what the underlying differences are first of all ?
The EFR register is as you wrote adjusted differently.
> If you just need to adjust a register differently then override
> serial_in/serial_out methods and figure out how to detect your device
> against others (or a way to probe it somehow).
I'm a bit in doubt as to which conclusions I am allowed to draw.
In 'autoconfig_16550a' I can see that a sepcific port type is set;
if (status1 == 6 && status2 == 7) {
up->port.type = PORT_16750;
up->capabilities |= UART_CAP_AFE | UART_CAP_SLEEP;
return;
}
My particular uart resports (status1 == 6 && status2 == 6). If that is good
enough I can add another porttype and add the correct register address as
UART_EXAR_EFR in the header file.
Another thought could be to write 0xFF (or some other value) to the correct
EFR-register and read that byte to test if the register is present. The
problem here is that I do not how the bus reacts to writting/reading invalid
addresses.
--
Søren Holm
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-30 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 10:17 Hardware flowcontrol on XR17D154 Søren holm
2011-08-30 10:34 ` Alan Cox
2011-08-30 11:27 ` Søren holm [this message]
2011-08-30 12:32 ` Alan Cox
2011-08-30 13:14 ` Søren holm
2011-09-02 10:20 ` Søren holm
2011-09-02 12:28 ` Alan Cox
2011-09-02 20:52 ` [PATCH] serial: Support the EFR-register of XR1715x uarts Søren Holm
2011-09-02 20:55 ` Søren Holm
2011-09-03 10:47 ` Alan Cox
2011-09-02 21:11 ` Hardware flowcontrol on XR17D154 Søren holm
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=201108301327.04542.sgh@sgh.dk \
--to=sgh@sgh.dk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-serial@vger.kernel.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 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.