All of lore.kernel.org
 help / color / mirror / Atom feed
From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 16/23] at91: Make LCD controller device common
Date: Thu, 21 Apr 2011 19:13:08 +1200	[thread overview]
Message-ID: <4DAFD904.409@bluewatersys.com> (raw)
In-Reply-To: <20110421070227.GF31131@pengutronix.de>

On 21/04/11 19:02, Uwe Kleine-K?nig wrote:
> Hello Ryan,
> 
> On Thu, Apr 21, 2011 at 05:42:08PM +1200, Ryan Mallon wrote:
>> Replace the individual LCD controller device code for each at91 variant with a
>> single implementation in devices.c
>>
>> Signed-off-by: Ryan Mallon <ryan@bluewatersys.com>

<snip>

>> +static struct platform_device at91_lcdc_device = {
>> +	.name		= "atmel_lcdfb",
>> +	.id		= 0,
>> +	.dev		= {
>> +				.dma_mask		= &lcdc_dmamask,
>> +				.coherent_dma_mask	= DMA_BIT_MASK(32),
>> +				.platform_data		= &lcdc_data,
>> +	},
>> +	.resource	= lcdc_resources,
>> +	.num_resources	= ARRAY_SIZE(lcdc_resources),
>> +};
> One difference to my approach (which you can like or not) is that mxc
> uses dynamic allocation of the platform_devices. A struct
> platform_device has a size of 320 bytes. So instead of using
> at91_lcdc_device you could add to at91_add_device_lcdc:
> 
> 	struct platform_device *pdev = platform_device_register_resndata(
> 		NULL, "atmel_lcdfb", 0, &lcdc_resources,
> 		ARRAY_SIZE(lcdc_resources), *data, sizeof(*data));
> 
> with the added benefit that lcdc_resources and *data can be __initdata
> (or __initconst) to save a few more bytes.
> 
> The obvious downside is that dynamic allocation probably takes more time
> than using static data and so increases the boottime. I didn't measure
> it, but I think the difference is small enough to see over it.

Having the resources and *data also be __initdata would be good. One
reason I have taken the approach I have, rather than what you suggest,
is that my patches introduce minimal change. To create the common
devices.c I have cut and pasted one of the implementations and only made
necessary changes to make it generic to all of the variants rather than
do a complete rewrite. I think that this approach makes the patch series
easier to review and more likely to be correct (less new bugs introduced).

~Ryan

  reply	other threads:[~2011-04-21  7:13 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  5:41 [PATCH v2 00/23] at91: Replace duplicate device initialisation code with Ryan Mallon
2011-04-21  5:41 ` [PATCH v2 01/23] at91: Add common devices framework Ryan Mallon
2011-04-21  5:41 ` [PATCH v2 02/23] at91: Make Ethernet device common Ryan Mallon
2011-04-21 23:02   ` H Hartley Sweeten
2011-04-25 20:16     ` Ryan Mallon
2011-04-26  4:35       ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-26  5:26         ` Ryan Mallon
2011-04-21 23:19   ` H Hartley Sweeten
2011-04-25 20:15     ` Ryan Mallon
2011-04-28  9:15     ` Russell King - ARM Linux
2011-04-28 17:57       ` H Hartley Sweeten
2011-04-28 18:31         ` Russell King - ARM Linux
2011-04-28 20:46           ` H Hartley Sweeten
2011-04-29 19:32           ` Uwe Kleine-König
2011-04-28 21:34       ` Ryan Mallon
2011-04-28 21:54         ` Russell King - ARM Linux
2011-04-21  5:41 ` [PATCH v2 03/23] at91: Make USB OHCI/EHCI devices common Ryan Mallon
2011-04-21  5:41 ` [PATCH v2 04/23] at91: Make UDC device common Ryan Mallon
2011-04-21  5:41 ` [PATCH v2 05/23] at91: Make MMC " Ryan Mallon
2011-04-21  5:41 ` [PATCH v2 06/23] at91: Make NAND " Ryan Mallon
2011-04-21  5:41 ` [PATCH v2 07/23] at91: Make TWI " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 08/23] at91: Make SPI " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 09/23] at91: Make TCB " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 10/23] at91: Make RTT " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 11/23] at91: Make watchdog " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 13/23] at91: Make PWM " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 14/23] at91: Make SSC " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 15/23] at91: Make AC97 " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 16/23] at91: Make LCD controller " Ryan Mallon
2011-04-21  7:02   ` Uwe Kleine-König
2011-04-21  7:13     ` Ryan Mallon [this message]
2011-04-21 12:43     ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-21  5:42 ` [PATCH v2 17/23] at91: Make touchscreen " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 18/23] at91: Make HDMAC " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 19/23] at91: Make RTC " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 20/23] at91: Make high speed USB gadget " Ryan Mallon
2011-04-21 21:21   ` H Hartley Sweeten
2011-04-21 21:28     ` Ryan Mallon
2011-04-21 21:53       ` H Hartley Sweeten
2011-04-21  5:42 ` [PATCH v2 21/23] at91: Make compact flash " Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 22/23] at91: Move at91sam9263 CAN device to common devices Ryan Mallon
2011-04-21  5:42 ` [PATCH v2 23/23] at91: Remove mAgic and ISI device code Ryan Mallon
2011-04-21 17:33   ` H Hartley Sweeten
2011-04-21 20:12     ` Ryan Mallon
2011-04-26  4:39       ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-26  5:30         ` Ryan Mallon
2011-04-28  9:19       ` Russell King - ARM Linux
2011-04-28  9:23         ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-21  5:43 ` [PATCH v2 12/23] at91: Make UART devices common Ryan Mallon
2011-04-21 17:02 ` [PATCH v2 00/23] at91: Replace duplicate device initialisation code with H Hartley Sweeten

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=4DAFD904.409@bluewatersys.com \
    --to=ryan@bluewatersys.com \
    --cc=linux-arm-kernel@lists.infradead.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.