Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: J.Weitzel@phytec.de (Jan Weitzel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4: PCM049: remove vusim regulator
Date: Fri, 15 Jul 2011 11:47:54 +0200	[thread overview]
Message-ID: <1310723274.26087.38.camel@lws-weitzel> (raw)
In-Reply-To: <20110715075024.GO5783@atomide.com>

Am Freitag, den 15.07.2011, 00:50 -0700 schrieb Tony Lindgren:
> Well we can add it even before device tree support if it makes
> sense from code coalescing point of view. In this case it would
> mean creating board-panda-common.c or similar so the code can
> be shared amongst the panda variants.
> 
> It seems that some GPIO pins are different and there are some
> difference in devices connected, but big parts of the code can be
> shared.
> 
> Adding the pending boards without combining code would be adding code
> that will be going away for most part with the device tree support.
> 
> And most likely the beagle and panda based boards will be the first
> ones to work with device tree. So anything we can do to have common
> board init code will also help with this effort.
> 
> Regards,
> 
> Tony
pcm049 and panda board have some more different devices.
I am working on patches to add NAND support and using tlv320aic3x audio
codec which need regulators in platformcode. I need a hack to controll
usb otg by gpio (controlling a external power circuit). The patches are
not mainline ready by now. 
If using machine_is_xxxx() in board-omap4panda.c then also is good way,
I could provide our board as patches on top of board-omap4panda.c.
When will pandaboard use device tree to boot?

Kind Regards,
Jan

  parent reply	other threads:[~2011-07-15  9:47 UTC|newest]

Thread overview: 25+ 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 [this message]
2011-07-15 10:55                           ` Tony Lindgren
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=1310723274.26087.38.camel@lws-weitzel \
    --to=j.weitzel@phytec.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox