From: Tony Lindgren <tony@atomide.com>
To: Jan Weitzel <j.weitzel@phytec.de>
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC 2/2] omap4: board-omap4pcm049: add Phytec phyCORE-OMAP4
Date: Thu, 21 Jul 2011 00:38:34 -0700 [thread overview]
Message-ID: <20110721073833.GD5783@atomide.com> (raw)
In-Reply-To: <1311075927-5562-3-git-send-email-j.weitzel@phytec.de>
* Jan Weitzel <j.weitzel@phytec.de> [110719 04:40]:
> --- a/arch/arm/mach-omap2/Makefile
> +++ b/arch/arm/mach-omap2/Makefile
> @@ -240,6 +240,10 @@ obj-$(CONFIG_MACH_OMAP4_PANDA) += board-omap4panda.o \
> board-omap4panda-common.o \
> hsmmc.o \
> omap_phy_internal.o
> +obj-$(CONFIG_MACH_MACH_PCM049) += board-pcm049.o \
^^^^
Extra mach above?
> + board-omap4panda-common.o \
> + hsmmc.o \
> + omap_phy_internal.o
>
> obj-$(CONFIG_MACH_OMAP3517EVM) += board-am3517evm.o \
> omap_phy_internal.o \
Maybe use just board-panda-common.o here instead? And in the Makefile
it can be compiled in with something like:
obj-$(CONFIG_MACH_OMAP4_PANDA) += board-panda-common.o
obj-$(CONFIG_MACH_PCM049) += board-panda-common.o
...
obj-$(CONFIG_MACH_OMAP4_PANDA) += board-omap4panda.o
obj-$(CONFIG_MACH_PCM049) += board-pcm049.o
...
I already posted a patch to get rid of repeating the hsmmc.o
for each board using it.
> +#include <linux/kernel.h>
> +#include <linux/init.h>
> +#include <linux/platform_device.h>
> +#include <linux/clk.h>
> +#include <linux/io.h>
> +#include <linux/leds.h>
> +#include <linux/gpio.h>
> +#include <linux/usb/otg.h>
> +#include <linux/i2c/twl.h>
> +#include <linux/i2c/at24.h>
> +#include <linux/mfd/stmpe.h>
> +#include <linux/leds-pca9532.h>
> +#include <linux/regulator/machine.h>
> +#include <linux/regulator/fixed.h>
> +#include <linux/wl12xx.h>
> +#include <linux/smsc911x.h>
> +
> +#include <mach/hardware.h>
> +#include <mach/omap4-common.h>
> +#include <asm/mach-types.h>
> +#include <asm/mach/arch.h>
> +#include <asm/mach/map.h>
> +#include <video/omapdss.h>
> +
> +#include <plat/board.h>
> +#include <plat/common.h>
> +#include <plat/usb.h>
> +#include <plat/gpmc.h>
> +#include <plat/gpmc-smsc911x.h>
> +#include <plat/mmc.h>
> +#include <video/omap-panel-generic-dpi.h>
> +
> +#include "hsmmc.h"
> +#include "control.h"
> +#include "mux.h"
> +#include "common-board-devices.h"
> +#include "board-omap4panda-common.h"
Maybe check which includes are now needed with the panda-common?
> +struct omap_dss_device pcm049_dpi_device = {
> + .type = OMAP_DISPLAY_TYPE_DPI,
> + .name = "dpi",
> + .driver_name = "generic_dpi_panel",
> + .data = &omap4_dpi_panel,
> + .phy.dpi.data_lines = 24,
> + .channel = OMAP_DSS_CHANNEL_LCD2,
> +};
Usually tabs are used for aligning the structs like above..
> +static struct omap_dss_device pcm049_dvi_device = {
> + .name = "dvi",
> + .driver_name = "hdmi_panel",
> + .type = OMAP_DISPLAY_TYPE_HDMI,
.. so please align the structs with tabs for the new data too.
Please check the data structs in all your patches while at it.
Also looks like there's an extra space above before
pcm049_dvi_device.
> +static struct stmpe_platform_data pba_stm_pdata = {
> + .blocks = STMPE_BLOCK_GPIO | STMPE_BLOCK_TOUCHSCREEN,
> + .irq_base = TWL6030_IRQ_END,
> + .irq_trigger = IRQF_TRIGGER_RISING,
> + .irq_invert_polarity = true,
> + .gpio = &pba_gpio_stm_data,
> + .ts = &pba_ts_stm_pdata,
> +};
Here too please check the alignment.
Regards,
Tony
next prev parent reply other threads:[~2011-07-21 7:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 10:04 [PATCH 0/3] ARM:OMAP4 add Phytec phyCORE-OMAP4 board Jan Weitzel
2011-07-08 10:04 ` [PATCH 1/3] ARM: OMAP4: Add pcm049 to Kconfig/Makefile Jan Weitzel
2011-07-08 11:49 ` Sergei Shtylyov
2011-07-08 11:55 ` Tony Lindgren
2011-07-08 11:58 ` Felipe Balbi
2011-07-14 7:27 ` Tony Lindgren
2011-07-14 7:47 ` Tony Lindgren
2011-07-08 12:21 ` [PATCH v2] ARM:OMAP4 add Phytec phyCORE-OMAP4 board Jan Weitzel
2011-07-13 8:03 ` Tony Lindgren
2011-07-13 10:58 ` Jan Weitzel
2011-07-13 10:59 ` [PATCH] ARM: OMAP4: PCM049: remove vusim regulator Jan Weitzel
2011-07-13 12:13 ` Sergei Shtylyov
2011-07-13 12:54 ` [PATCH v2] " Jan Weitzel
2011-07-13 12:56 ` [PATCH] " Jan Weitzel
2011-07-14 7:34 ` Tony Lindgren
2011-07-14 8:39 ` Jan Weitzel
2011-07-15 7:50 ` Tony Lindgren
2011-07-15 7:58 ` Felipe Balbi
2011-07-15 8:20 ` Tony Lindgren
2011-07-15 8:31 ` Felipe Balbi
2011-07-15 10:59 ` Tony Lindgren
2011-07-15 9:47 ` Jan Weitzel
2011-07-15 10:55 ` Tony Lindgren
2011-07-15 16:06 ` [RFC 0/2] join omap4panda and pcm049 Jan Weitzel
2011-07-18 8:42 ` Tony Lindgren
2011-07-19 11:45 ` [RFC 0/2 v2] " Jan Weitzel
2011-07-19 11:45 ` [RFC 1/2] omap4: board-omap4panda: prepare for join Jan Weitzel
2011-07-21 7:25 ` Tony Lindgren
2011-07-19 11:45 ` [RFC 2/2] omap4: board-omap4pcm049: add Phytec phyCORE-OMAP4 Jan Weitzel
2011-07-21 7:38 ` Tony Lindgren [this message]
2011-07-15 16:06 ` [PATCH 1/2] omap4: board-omap4panda: prepare for join Jan Weitzel
2011-07-15 16:06 ` [PATCH 2/2] omap4: board-omap4panda: join Phytec phyCORE-OMAP4 Jan Weitzel
2011-07-08 10:04 ` [PATCH 2/3] ARM: OMAP4: add pcm049 DEBUGLL Jan Weitzel
2011-07-08 10:04 ` [PATCH 3/3] ARM: OMAP4: platformcode board-omap4pcm049.c Jan Weitzel
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=20110721073833.GD5783@atomide.com \
--to=tony@atomide.com \
--cc=j.weitzel@phytec.de \
--cc=linux-omap@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).