linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org
Cc: Matt Porter <mporter@ti.com>, Sekhar Nori <nsekhar@ti.com>,
	linux-kernel@vger.kernel.org, "Manjunathappa,
	Prakash" <prakash.pm@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-next@vger.kernel.org
Subject: linux-next: manual merge of the arm-soc tree with the omap_dss2 tree
Date: Fri, 30 Nov 2012 16:18:56 +1100	[thread overview]
Message-ID: <20121130161856.985bdeb55e3a9be322e772ec@canb.auug.org.au> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2956 bytes --]

Hi all,

Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mach-davinci/devices-da8xx.c between commit 3b43ad201dea
("da8xx-fb: cleanup LCDC configurations") from the omap_dss2 tree and
commit 8e0d72d2c7a6 ("ARM: davinci: da8xx: add DA850 PRUSS support") from
the arm-soc tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/arm/mach-davinci/devices-da8xx.c
index fcb30d3,46c9a0c..0000000
--- a/arch/arm/mach-davinci/devices-da8xx.c
+++ b/arch/arm/mach-davinci/devices-da8xx.c
@@@ -518,9 -520,98 +520,78 @@@ void __init da8xx_register_mcasp(int id
  	}
  }
  
+ static struct resource da8xx_pruss_resources[] = {
+ 	{
+ 		.start	= DA8XX_PRUSS_MEM_BASE,
+ 		.end	= DA8XX_PRUSS_MEM_BASE + 0xFFFF,
+ 		.flags	= IORESOURCE_MEM,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT0,
+ 		.end	= IRQ_DA8XX_EVTOUT0,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT1,
+ 		.end	= IRQ_DA8XX_EVTOUT1,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT2,
+ 		.end	= IRQ_DA8XX_EVTOUT2,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT3,
+ 		.end	= IRQ_DA8XX_EVTOUT3,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT4,
+ 		.end	= IRQ_DA8XX_EVTOUT4,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT5,
+ 		.end	= IRQ_DA8XX_EVTOUT5,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT6,
+ 		.end	= IRQ_DA8XX_EVTOUT6,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ 	{
+ 		.start	= IRQ_DA8XX_EVTOUT7,
+ 		.end	= IRQ_DA8XX_EVTOUT7,
+ 		.flags	= IORESOURCE_IRQ,
+ 	},
+ };
+ 
+ static struct uio_pruss_pdata da8xx_uio_pruss_pdata = {
+ 	.pintc_base	= 0x4000,
+ };
+ 
+ static struct platform_device da8xx_uio_pruss_dev = {
+ 	.name		= "pruss_uio",
+ 	.id		= -1,
+ 	.num_resources	= ARRAY_SIZE(da8xx_pruss_resources),
+ 	.resource	= da8xx_pruss_resources,
+ 	.dev		= {
+ 		.coherent_dma_mask	= DMA_BIT_MASK(32),
+ 		.platform_data		= &da8xx_uio_pruss_pdata,
+ 	}
+ };
+ 
+ int __init da8xx_register_uio_pruss(void)
+ {
+ 	da8xx_uio_pruss_pdata.sram_pool = sram_get_gen_pool();
+ 	return platform_device_register(&da8xx_uio_pruss_dev);
+ }
+ 
 -static const struct display_panel disp_panel = {
 -	QVGA,
 -	16,
 -	16,
 -	COLOR_ACTIVE,
 -};
 -
  static struct lcd_ctrl_config lcd_cfg = {
 -	&disp_panel,
 -	.ac_bias		= 255,
 -	.ac_bias_intrpt		= 0,
 -	.dma_burst_sz		= 16,
 +	.panel_shade		= COLOR_ACTIVE,
  	.bpp			= 16,
 -	.fdd			= 255,
 -	.tft_alt_mode		= 0,
 -	.stn_565_mode		= 0,
 -	.mono_8bit_mode		= 0,
 -	.invert_line_clock	= 1,
 -	.invert_frm_clock	= 1,
 -	.sync_edge		= 0,
 -	.sync_ctrl		= 1,
 -	.raster_order		= 0,
 -	.fifo_th		= 6,
  };
  
  struct da8xx_lcdc_platform_data sharp_lcd035q3dg01_pdata = {

[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2012-11-30  5:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  5:18 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-09  7:40 linux-next: manual merge of the arm-soc tree with the omap_dss2 tree Stephen Rothwell
2013-04-09  9:32 ` Arnd Bergmann
2012-12-03  5:52 Stephen Rothwell
2012-11-26 10:56 Stephen Rothwell
2012-11-26 15:53 ` Tony Lindgren
2012-09-24  9:53 Stephen Rothwell
2012-09-24 12:43 ` Arnd Bergmann
2012-09-24 13:11   ` Tomi Valkeinen
2012-09-24 16:19     ` Tony Lindgren
2012-09-17  9:23 Stephen Rothwell
2012-05-14  8:51 Stephen Rothwell
2012-03-13  8:21 Stephen Rothwell
2012-03-09  7:09 Stephen Rothwell
2012-03-08  6:00 Stephen Rothwell
2012-03-08 16:16 ` Arnd Bergmann
2012-03-09  9:35   ` Tomi Valkeinen
2012-03-09 11:50     ` Arnd Bergmann
2012-03-09 12:14       ` Tomi Valkeinen
2012-03-09 12:26         ` Arnd Bergmann
2012-03-09 12:31           ` Tomi Valkeinen
2012-03-08  5:58 Stephen Rothwell
2012-03-08  5:55 Stephen Rothwell
2012-03-08  5:51 Stephen Rothwell
2012-03-10  9:55 ` Janusz Krzysztofik

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=20121130161856.985bdeb55e3a9be322e772ec@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mporter@ti.com \
    --cc=nsekhar@ti.com \
    --cc=olof@lixom.net \
    --cc=prakash.pm@ti.com \
    --cc=tomi.valkeinen@ti.com \
    /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).