From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-DM] List of offending drivers
Date: Fri, 27 Jul 2012 03:11:04 +0200 [thread overview]
Message-ID: <201207270311.04978.marex@denx.de> (raw)
In-Reply-To: <CALButCJMqBQ1-j-YMk8T8-n2nYvji6y4jseSUHjqNaB5aL0+kQ@mail.gmail.com>
Dear Graeme Russ,
> Hi Marek,
>
> On Fri, Jul 27, 2012 at 9:18 AM, Marek Vasut <marex@denx.de> wrote:
> > Hello,
> >
> > Check the following list, it's the list of drivers scattered (misplaced)
> > across the tree. The list is not complete and might be inaccurate. But
> > it should give a good impression of what I'm going to break soon:
> >
> > arch/x86/cpu/sc520/sc520_pci.c
> > board/eNET/eNET_pci.c
>
> Hmm, I'm wondering what where the line between 'driver' and 'arch/board
> specific driver glue' is?
That's why I said the list isn't exactly precise.
> How was this list generated?
By hard manual labor (=slavework).
> You seem to have missed sc520_ssi.c and sc520_timer.c
I wonder if we should move the timer drivers ... maybe to drivers/timer/ ?
> board/eNET/eNET_pci.c only contains:
>
> pci_enet_fixup_irq() - Board specific configuration of PCI interrupt lines.
> This is a platform function which is specified when the board initialises
> the PCI driver. Note that this function calls pci_sc520_set_irq() which is
> located on arch/x86/cpu/sc520/sc520_pci.c (see below)
Ok, so this one should be left out, I didn't properly examine them all. Just
wanted to share the list, the examination will follow this weekend, when I start
moving them.
> pci_init_board() - One line wrapper for pci_sc520_init() which should get
> dropped once the driver model and init sequence (if that gets looked at
> again) refactoring
>
> pci_set_regions() - Configure the board-specific PCI memory and I/O regions
>
> arch/x86/cpu/sc520/sc520_pci.c contains:
> pci_sc520_set_irq() - A support function for board-specific PCI interrupt
> line configuration
> pci_sc520_init() - SC520 specific PCI driver initialisation
>
> So neither of these files are 'drivers' per-se. They are really just
> initialisation and platform specific support functions. How do these fit
> into the new driver model?
You can supply a pointer to that function to some "pci" driver I guess ...
Pavel?
> Regards,
>
> Graeme
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-27 1:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 23:18 [U-Boot] List of offending drivers Marek Vasut
2012-07-27 1:08 ` [U-Boot] [U-Boot-DM] " Graeme Russ
2012-07-27 1:11 ` Marek Vasut [this message]
2012-07-27 1:20 ` Graeme Russ
2012-07-27 1:26 ` Marek Vasut
2012-07-27 1:29 ` Graeme Russ
2012-07-27 1:37 ` Marek Vasut
2012-07-27 4:41 ` Wolfgang Denk
2012-07-27 8:42 ` Marek Vasut
2012-07-27 9:33 ` Wolfgang Denk
2012-07-31 7:50 ` Mike Frysinger
2012-07-27 6:28 ` [U-Boot] " Lukasz Majewski
2012-07-27 8:43 ` Marek Vasut
2012-07-27 14:11 ` Igor Grinberg
2012-07-27 14:30 ` Marek Vasut
2012-07-27 14:45 ` Igor Grinberg
2012-07-27 14:49 ` Marek Vasut
2012-08-01 10:11 ` [U-Boot] [U-Boot-DM] " Andreas Bießmann
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=201207270311.04978.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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