All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] sparc32,leon: added LEON-common low-level PCI
Date: Mon, 23 May 2011 16:10:58 +0000	[thread overview]
Message-ID: <4DDA8712.6000309@gaisler.com> (raw)
In-Reply-To: <1305964529-8577-1-git-send-email-daniel@gaisler.com>

Julian Calaby wrote:

>On Sat, May 21, 2011 at 21:33, Sam Ravnborg <sam@ravnborg.org> wrote:
>  
>
>>On Sat, May 21, 2011 at 09:55:28AM +0200, Daniel Hellstrom wrote:
>>    
>>
>>>The LEON architecture does not have a BIOS or bootloader that
>>>initializes PCI for us, instead Linux generic PCI layer is used
>>>to set up resources and IRQ.
>>>
>>>Signed-off-by: Daniel Hellstrom <daniel@gaisler.com>
>>>      
>>>
>>Hi Daniel.
>>
>>Reading through this patch it looks like LEOON pci support is bolted on top
>>of what we have rather than trying to integrate it a bit more.
>>
>>I would like to see something like:
>>
>>* include/asm/pcic.h intregated in pci_32.h
>>    
>>
Do we really want that? I mean drivers that include pci.h does not need 
to know about pcic.h internals. I think is is quite clear the way it is, 
pcic.h is one PCI Host controller implementation, the host 
implementation shouldn't go to the header right? This is similar to 
LEON_PCI, is a common file for LEON PCI host controllers on the LEON 
platform. PCIC is common to machines which have PCI on the SUN platform.

>>* leon specifics added to pci_32.h - with minimal ifdefs
>>    
>>
Ok, could do that. Then I propose that I remove pci_leon.h, add some of 
that stuff into pci_32.h (will still be as many ifdefs as before) and I 
will create a leon_pci.h similar to pcic.h or add LEON-PCI specific 
stuff that nowone really wants to know about 
(leon_pci_info,leon_pci_init), or I add it to leon.h instead.

>>Dunno abot the rest...
>>
>>If i find time I will try to come up with a proposal later tonight.
>>
>>       Sam
>>    
>>
>
>When I looked at this earlier, I was thinking that we might want to
>introduce a new KConfig variable, maybe CONFIG_LEON_PCI, to hide all
>this stuff behind so we don't have to do any complicated ifdefery or
>change any existing ifdefs.
>  
>
Ok, I will try to add a PCIC and a LEON_PCI config option. Then most 
ifdefs still will be there but only dependent on one thing: PCIC, 
LEON_PCI or PCI.

Does all this sound reasonable?

Daniel

      parent reply	other threads:[~2011-05-23 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21  7:55 [PATCH 1/2 v2] sparc32,leon: added LEON-common low-level PCI routines Daniel Hellstrom
2011-05-21 11:33 ` [PATCH 1/2 v2] sparc32,leon: added LEON-common low-level PCI Sam Ravnborg
2011-05-21 12:49 ` [PATCH 1/2 v2] sparc32,leon: added LEON-common low-level PCI routines Julian Calaby
2011-05-23 16:10 ` Daniel Hellstrom [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=4DDA8712.6000309@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=sparclinux@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.