All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Several questions about SH PCI
Date: Tue, 15 Jul 2008 08:58:01 +0000	[thread overview]
Message-ID: <20080715085801.GA23440@linux-sh.org> (raw)
In-Reply-To: <7b5883fc0807101148g601033e3n4f9ec4a53ed628fa@mail.gmail.com>

On Thu, Jul 10, 2008 at 09:48:41PM +0300, Roni Feldman wrote:
> 1. In arch/sh/driver/pci/pci-sh7751.c, shouldn't sh7751_pci_init() be
> tagged as core_initcall and not subsyss_initcall? pcibios_init(),
> which scans the bus (and expects the pcic to be already initialized)
> is also tagged as subsys_initcall. This might lead to bad ordering in
> case more things are introduced in the subsys section, since there's
> no order guarantee for functions in the same section, right?
> 
It's link order dependent, but yes, there's a potential issue here if we
start out with the PCIC completely disabled at boot time.

> 2. I didn't manage to find PCIDMA support in the kernel. Did I
> overlook it or is it just something nobody has implemented yet for sh?
> 
It's not been implemented. Feel free to send patches.

> 3. I was thinking about the case where I'm using non-DMA PCI access,
> and I need to change my window (PCIMBR or PCIIOBR). In that case every
> section that changes the MBR / IOBR and does PCI access need to be
> enclosed in something like pci_lock() and pci_unlock(), to solve the
> problem of some other task changing MBR in my "critical section".
> Would spinlocks be the best way to implement these locks?
> 
Yes.

      reply	other threads:[~2008-07-15  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 18:48 Several questions about SH PCI Roni Feldman
2008-07-15  8:58 ` Paul Mundt [this message]

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=20080715085801.GA23440@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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.