linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arve@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/10] goldfish: add the goldfish virtual bus
Date: Thu, 10 Jan 2013 15:54:15 +0000	[thread overview]
Message-ID: <20130110155415.52920a41@bob.linux.org.uk> (raw)
In-Reply-To: <201301092230.40331.arnd@arndb.de>

> Maybe drivers/bus would be more appropriate though. Every platform
> handles platforms differently, and x86 seems to be the only one that
> likes the model of putting stuff under drivers/platform.

I'm fine with that and I agree - it is a bus.

> __devinit/__devexit are going away, so you can skip adding them
> for new code.

I'll strip those out of the upstream version

> > +module_init(goldfish_pdev_bus_init);
> > +module_exit(goldfish_pdev_bus_exit);
> 
> The module_platform_driver() macro takes care of this.

Will change to that.

> 
> > +static struct resource goldfish_pdev_bus_resources[] = {
> > +	{
> > +		.start  = GOLDFISH_PDEV_BUS_BASE,
> > +		.end    = GOLDFISH_PDEV_BUS_BASE +
> > GOLDFISH_PDEV_BUS_END - 1,
> > +		.flags  = IORESOURCE_IO,
> > +	},
> > +	{
> > +		.start	= GOLDFISH_PDEV_BUS_IRQ,
> > +		.end	= GOLDFISH_PDEV_BUS_IRQ,
> > +		.flags	= IORESOURCE_IRQ,
> > +	}
> > +};
> > +
> > +struct platform_device goldfish_pdev_bus_device = {
> > +	.name = "goldfish_pdev_bus",
> > +	.id = -1,
> > +	.num_resources = ARRAY_SIZE(goldfish_pdev_bus_resources),
> > +	.resource = goldfish_pdev_bus_resources
> > +};
> > +
> > +static int __init goldfish_init(void)
> > +{
> > +	return platform_device_register(&goldfish_pdev_bus_device);
> > +}
> > +device_initcall(goldfish_init);
> 
> This is the part that I think should actually be part of the
> architecture tree.

Thinking about it a bit I agree. We still end up needing an
architectural header for early console and the like eventually but it
does eliminate much of the rest.

I'll rework it that way.

Alan

  reply	other threads:[~2013-01-10 15:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 14:22 [PATCH 00/10] goldfish: rebase/resend versus current -next Alan Cox
2013-01-09 14:22 ` [PATCH 01/10] goldfish: definitions for Goldfish on x86 platforms Alan Cox
2013-01-09 14:23 ` [PATCH 02/10] goldfish: add the goldfish virtual bus Alan Cox
2013-01-09 22:30   ` Arnd Bergmann
2013-01-10 15:54     ` Alan Cox [this message]
2013-01-09 14:23 ` [PATCH 03/10] goldfish: tty driver Alan Cox
2013-01-09 22:33   ` Arnd Bergmann
2013-01-09 14:24 ` [PATCH 04/10] goldfish: virtual input event driver Alan Cox
2013-01-09 14:24 ` [PATCH 05/10] goldfish: framebuffer Alan Cox
2013-01-09 14:24 ` [PATCH 06/10] goldfish: emulated MMC device Alan Cox
2013-01-09 14:25 ` [PATCH 07/10] goldfish: power device Alan Cox
2013-01-09 14:25 ` [PATCH 08/10] goldfish: real time clock Alan Cox
2013-01-09 14:25 ` [PATCH 09/10] goldfish: add QEMU pipe driver Alan Cox
2013-01-09 14:26 ` [PATCH 10/10] goldfish: NAND flash driver Alan Cox
2014-03-10 15:39 ` [PATCH 00/10] goldfish: rebase/resend versus current -next Guennadi Liakhovetski
  -- strict thread matches above, loose matches on Subject: below --
2013-01-16 16:58 [PATCH 00/10] goldfish: still swimming Alan Cox
2013-01-16 16:58 ` [PATCH 02/10] goldfish: add the goldfish virtual bus Alan Cox
2013-01-16 16:57   ` Felipe Balbi
2013-01-17 17:53 [PATCH 00/10] goldish: onwards, upwards 8) Alan Cox
2013-01-17 17:54 ` [PATCH 02/10] goldfish: add the goldfish virtual bus Alan Cox

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=20130110155415.52920a41@bob.linux.org.uk \
    --to=alan@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=arve@android.com \
    --cc=linux-kernel@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 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).