linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: linuxppc-dev@ozlabs.org
Subject: [RFC]PPC driver lock for DMA registers
Date: Wed, 18 Mar 2009 09:29:13 -0700	[thread overview]
Message-ID: <49C12159.4060100@embeddedarm.com> (raw)

Hello,

I'm working on SD card and Nand drivers that I would like to eventually submit 
for inclusion in the mainline kernel. This being my first kernel port being 
submitted upstream I was hoping for comments on my proposed design to ensure it 
would be excepted in the mainline kernel(from a design standpoint). We have an 
FPGA on our product that has an interface for transferring data via DMA. The SD 
card driver and Nand flash driver will both be accessing these registers. As a 
result I was planning on writing a dma driver(drivers/dma/ts81xx.c) that 
implements a function dma_op() that gets passed a physical address, virtual 
address, length, and read/write op and returns an int. I'd use a semaphore to 
protect the registers. I'd also implement a function dma_bus_init() for 
allocating a cache coherent buffer, initializing the semaphore, and ioremapping 
the FPGA regs.

I'd really appreciate any feedback or suggestions.

-- 
Best Regards,
________________________________________________________________
  Eddie Dawydiuk, Technologic Systems | voice:  (480) 837-5200
  16525 East Laser Drive 	     | fax:    (480) 837-5300
  Fountain Hills, AZ 85268            | web: www.embeddedARM.com

             reply	other threads:[~2009-03-18 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 16:29 Eddie Dawydiuk [this message]
2009-03-18 16:40 ` [RFC]PPC driver lock for DMA registers Grant Likely
2009-03-18 16:53   ` Eddie Dawydiuk

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=49C12159.4060100@embeddedarm.com \
    --to=eddie@embeddedarm.com \
    --cc=linuxppc-dev@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).