Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	macro@mips.com, Richard Sandiford <rsandifo@redhat.com>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] I/O helpers rework
Date: Thu, 17 Feb 2005 01:34:06 +0000	[thread overview]
Message-ID: <20050217013406.GA14909@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0501211739410.16576@blysk.ds.pg.gda.pl>

On Sat, Jan 22, 2005 at 02:51:47AM +0000, Maciej W. Rozycki wrote:

> > 1. How about using 'const void *' for outs*()/reads*() ?  This will
> >    remove some compiler warnings too.  Also, it seems 'volatile' for
> >    memory buffer are unneeded.
> > 
> > 2. In *in*()/*out*(), it would be better to call __swizzle_addr*()
> >    AFTER adding mips_io_port_base.  This unifies the meaning of the
> >    argument of __swizzle_addr*() (always virtual address).  Then,
> >    mach-specific __swizzle_addr*() can to every evil thing based on
> >    the argument.
> > 
> > 3. How about Moving generic ioswab*() to mangle-port.h ?  Also how
> >    about passing virtual address to *ioswab*() ?  Then we can provide
> >    mach-specific ioswab*() and can do every evil thing based on its
> >    argument.  It is usefull on machines which have regions with
> >    different endian conversion scheme.
> 
>  Thanks for your insight -- your comments are not lost and I am working on 
> taking them into account.  But meanwhile a confusion around the semantics 
> of these operations arose (there is no documentation on them and some 
> drivers expect some of these functions to swap, while others expect them 
> not to) and changes were made to the tree that invalidated some of the 
> fixes.  That needs to be addressed first and I expect another update to 
> the file.  Here's a patch I'm going to start with.  Functions it adds have 
> been named dma_* to indicate they are meant to preserve memory byte 
> ordering.

Looks good but I don't really like the dma_* name prefix as these functions
really have nothing to do with DMA - in fact they're the opposite.

  Ralf

  parent reply	other threads:[~2005-02-17 20:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 21:13 [PATCH] I/O helpers rework Maciej W. Rozycki
2005-01-06 15:45 ` Atsushi Nemoto
2005-01-10 15:28   ` Maciej W. Rozycki
2005-01-10 17:21     ` Atsushi Nemoto
2005-01-10 18:11       ` Maciej W. Rozycki
2005-01-11  0:53         ` Atsushi Nemoto
2005-01-13 18:12         ` Richard Sandiford
2005-01-13 18:25           ` Maciej W. Rozycki
2005-01-13 21:48             ` Richard Sandiford
2005-01-14  1:52               ` Atsushi Nemoto
2005-01-14 11:05                 ` Richard Sandiford
2005-01-14 19:57               ` Maciej W. Rozycki
2005-01-21 16:50   ` Atsushi Nemoto
2005-01-22  2:51     ` Maciej W. Rozycki
2005-01-25  1:09       ` Atsushi Nemoto
2005-02-17  1:34       ` Ralf Baechle [this message]
2005-02-18 19:44         ` Maciej W. Rozycki
2005-01-06 16:33 ` Herbert Valerio Riedel
2005-01-10 13:05   ` Maciej W. Rozycki
2005-01-10 14:46     ` Herbert Valerio Riedel
2005-01-10 14:49       ` Herbert Valerio Riedel
2005-01-14 20:07         ` Maciej W. Rozycki
2005-01-13 22:18 ` Manish Lachwani

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=20050217013406.GA14909@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --cc=rsandifo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox