From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] include/ns16550.h: Unify structure declaration for registers
Date: Thu, 30 Apr 2009 14:26:56 +0200 [thread overview]
Message-ID: <m28wlie38v.fsf@ohwell.denx.de> (raw)
In-Reply-To: <49F8A196.60202@pobox.com> (Shinya Kuribayashi's message of "Thu, 30 Apr 2009 03:51:02 +0900")
Hello Shinya,
> Detlev Zundel wrote:
>> As I said, I understand now why there were different data-types involved
>> although this was kind of non-obvious. So I take it, you had a working
>> configuration with REG_SIZE = 4, correct?
>
> I might be unclear. I used to use REG_SIZE = -16, as 16550 registers
> are located at 0, +0x10, +0x20, ..., .
Ah, so you actually maintain an out-of-tree port. How should I have
foreseen that I break something that I don't even have the code to?
> In this case, I don't think REG_SIZE = 4/-4 works. Let's see:
No surely not. My replies were based on the (wrong) assumption that
your board port was in U-Boot code.
> What I need is something like this:
>
> struct NS16550 {
> unsigned char prepad_rbr[3];
> unsigned char rbr;
> unsigned char postpad_rbr[12];
> :
> :
> };
>
> or this also might work,
>
> struct NS16550 {
> unsigned long rbr;
> unsigned long pre_padrbr[3];
> : ^^^^
> :
> };
>
> Makes sense?
Although I can see what you need, I would be lying if I said that this
makes sense to me.
>> Can you enlighten me, why exactly the 8-bit accesses do not work on your
>> hardware? Is this because of a "too simplistic" address decoding logic?
>> What endianness is your CPU using?
>
> I don't know much about precise hardware logics, but the byte addresses
> under 16-bytes-border are ignored. I'm using a big-endian mips machine.
This does not make much sense to me, sorry.
>> I see. Actually I was looking a lot at the Linux driver but was hoping
>> that we could away without introducing serial_{in,out}...
>
> In my horrible opinion, the combinations of base addres + reg_shift
> + iotype (char, long, or whatever), are simpler, more configurable,
> more slid, easy to use, than what we used to have or what you
> consolidated this time.
You lost me here.
You truly consider
static unsigned int serial_in(struct uart_8250_port *up, int offset)
{
unsigned int tmp;
int ret, flags;
offset = map_8250_in_reg(up, offset) << up->port.regshift;
spin_lock_irqsave(&lbi_lock, flags);
switch (up->port.iotype) {
case UPIO_HUB6:
outb(up->port.hub6 - 1 + offset, up->port.iobase);
ret = inb(up->port.iobase + 1);
break;
case UPIO_MEM:
case UPIO_DWAPB:
ret = readb(up->port.membase + offset);
break;
case UPIO_RM9000:
case UPIO_MEM32:
ret = readl(up->port.membase + offset);
break;
#ifdef CONFIG_SERIAL_8250_AU1X00
case UPIO_AU:
ret = __raw_readl(up->port.membase + offset);
break;
#endif
case UPIO_TSI:
if (offset == UART_IIR) {
tmp = readl(up->port.membase + (UART_IIR & ~3));
ret = (tmp >> 16) & 0xff; /* UART_IIR % 4 == 2*/
} else
ret = readb(up->port.membase + offset);
break;
default:
ret = inb(up->port.iobase + offset);
break;
}
spin_unlock_irqrestore(&lbi_lock, flags);
return ret;
}
to be "simpler and more solid" readb(struct->field) (which is
effectively what we have in the current implementation)? You consider
"more configurable" to be a good in its own?
If your answers to these questions are yes, then we have different ideas
of writing code.
>> diff --git a/include/ns16550.h b/include/ns16550.h
>> index ce606b5..7924396 100644
>> --- a/include/ns16550.h
>> +++ b/include/ns16550.h
>> @@ -21,16 +21,20 @@
>> * will not allocate storage for arrays of size 0
>> */
>> +#if !defined(CONFIG_SYS_NS16550_REG_TYPE)
>> +#define UART_REG_TYPE unsigned char
>> +#endif
>> +
>> #if !defined(CONFIG_SYS_NS16550_REG_SIZE) || (CONFIG_SYS_NS16550_REG_SIZE == 0)
>> #error "Please define NS16550 registers size."
>> #elif (CONFIG_SYS_NS16550_REG_SIZE > 0)
>> -#define UART_REG(x) \
>> - unsigned char prepad_##x[CONFIG_SYS_NS16550_REG_SIZE - 1]; \
>> - unsigned char x;
>> +#define UART_REG(x) \
>> + UART_REG_TYPE prepad_##x[CONFIG_SYS_NS16550_REG_SIZE - sizeof(UART_REG_TYPE)]; \
>> + UART_REG_TYPE x;
>> #elif (CONFIG_SYS_NS16550_REG_SIZE < 0)
>> #define UART_REG(x) \
>> - unsigned char x; \
>> - unsigned char postpad_##x[-CONFIG_SYS_NS16550_REG_SIZE - 1];
>> + UART_REG_TYPE x; \
>> + UART_REG_TYPE postpad_##x[-CONFIG_SYS_NS16550_REG_SIZE - sizeof(UART_REG_TYPE)];
>> #endif
>> struct NS16550 {
>>
>>
>> Then you could do a
>>
>> #define CONFIG_SYS_NS16550_REG_SIZE 4
>> #define CONFIG_SYS_NS16550_REG_TYPE unsigned long
>>
>> This of course needs to be documented once it works ;)
>
> Looks to me like playing with macros...
This is not playing. I have better things to do if I want to play.
This was meant to be a solution for a problem which currently seems to
only exist in one special configuration, namely yours.
Best wishes
Detlev
--
LISP has jokingly been described as "the most intelligent way to misuse a
computer". I think that description a great compliment because it transmits
the full flavour of liberation: it has assisted a number of our most gifted
fellow humans in thinking previously impossible thoughts. - Edsger W. Dijkstra
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2009-04-30 12:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 14:45 [U-Boot] [PATCH] include/ns16550.h: Unify structure declaration for registers Detlev Zundel
2009-04-03 14:55 ` Detlev Zundel
2009-04-03 23:24 ` Wolfgang Denk
2009-04-25 1:21 ` Shinya Kuribayashi
2009-04-27 13:41 ` Detlev Zundel
2009-04-27 14:26 ` Shinya Kuribayashi
2009-04-27 15:36 ` Detlev Zundel
2009-04-27 16:09 ` Detlev Zundel
2009-04-29 18:51 ` Shinya Kuribayashi
2009-04-29 19:12 ` Shinya Kuribayashi
2009-04-30 13:30 ` Detlev Zundel
2009-04-30 14:10 ` Detlev Zundel
2009-05-01 0:56 ` Shinya Kuribayashi
2009-05-01 5:29 ` Shinya Kuribayashi
2009-04-30 12:26 ` Detlev Zundel [this message]
2009-04-30 12:52 ` Jerry Van Baren
2009-04-30 14:08 ` Detlev Zundel
2009-04-30 14:38 ` Detlev Zundel
2009-04-30 17:06 ` Jerry Van Baren
2009-05-01 2:21 ` Shinya Kuribayashi
2009-05-01 1:59 ` Shinya Kuribayashi
2009-05-04 15:40 ` Detlev Zundel
2009-05-04 21:21 ` Scott Wood
2009-05-04 21:57 ` Wolfgang Denk
2009-05-05 1:36 ` Shinya Kuribayashi
2009-05-05 9:09 ` Detlev Zundel
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=m28wlie38v.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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.