From: Sylvain Munaut <tnt@246tNt.com>
To: Andrey Volkov <avolkov@varma-el.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [00/02] MPC5200 Bestcomm platform driver
Date: Mon, 15 Aug 2005 15:37:17 +0200 [thread overview]
Message-ID: <43009A8D.1040704@246tNt.com> (raw)
In-Reply-To: <43006FD4.6060801@varma-el.com>
Hi Andrey,
Andrey Volkov wrote:
> Hi Sylvain
>
> This is first part of "platformizied" bestcomm/fec drivers.
>
> Comments/Commit?
Obviously I haven't yet had the time to review all the code but the
glance I had looked good ! I'll review it deeper and test it and come
back to you asap.
Still, some "preliminary" comments :
- I never really liked to have multiple "type" of buffer descriptors
depending of the number of pointers in them. "standard" task have
either 1 or 2 pointers true but I have custom tasks with 3 so I need a
subtmitbuffer3 ... Not very extensible imho. I think there is no problem
as defining the descriptor structure with an array of pointer and then
just allocate the good size at init. Whoever use them must anyway know
the number of pointer to fill.
- When I started to clean up bescomm a while ago, the only thing I
really got done was a rewrite of the SRAM allocator that supports the
freeing of block at little overcost. I'll try to find it and send it to you.
- I like the separation of phys/virt ;)
- sdma_clear_irq(struct sdma *s) is useless, interrupt acking for the
SDMA is already done in mpc52xx_irq.c
- I thought of separating bestcomm.h in two headers : one public for
the drivers that use the SDMA like the fec. one private for the
bestcomm.c and the tasks implementation. I think it makes sense but I
never deeply looked it one wouldn't end up almost empty.
... to be continued ;)
Sylvain
next prev parent reply other threads:[~2005-08-15 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 10:35 [00/02] MPC5200 Bestcomm platform driver Andrey Volkov
2005-08-15 13:37 ` Sylvain Munaut [this message]
2005-08-15 15:05 ` Andrey Volkov
2005-08-15 17:16 ` Dale Farnsworth
2005-08-15 17:51 ` Andrey Volkov
2005-08-22 13:41 ` Sylvain Munaut
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=43009A8D.1040704@246tNt.com \
--to=tnt@246tnt.com \
--cc=avolkov@varma-el.com \
--cc=linuxppc-embedded@ozlabs.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).