public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <menon.nishanth@gmail.com>
To: Dominic Curran <dcurran@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, saaguirre@ti.com
Subject: Re: [OMAPZOOM][PATCH] Testing for TWL4030 in board file change.
Date: Tue, 17 Feb 2009 10:11:31 +0200	[thread overview]
Message-ID: <499A7133.4050803@gmail.com> (raw)
In-Reply-To: <200902161815.13645.dcurran@ti.com>

Dominic Curran said the following on 02/17/2009 02:15 AM:
> From: Dominic Curran <dcurran@ti.com>
> Subject: [OMAPZOOM][PATCH] Testing for TWL4030 in board file change.
>
> This patch changes the method of testing for TWL4030 in the sensor portion of the 
> board file.
> Previously, if TWL4030 was not built into kernel then the build would be stopped 
> by code in the board file simular to:
>  #ifndef CONFIG_TWL4030_CORE
>  #error "no power companion board defined!"
>  #endif
>
> However for debugging purposes it maybe required to build without TWL4030.
> Therefore this patch allows the kernel to be compiled without a build error when 
> TWL4030 is not present.
> In such a case the sensor power function will build, but when called immediately 
> return a -ENODEV error (so initilization of sensor will go no further).
>
> This change is targeted at all camera sensors within the board files for SDP, 
> Zoom1 & Zoom2.
>
> Alternative fixes to this problem like changes to Kconfig were considered, but 
> rejected as inappropriate solutions.
>
>   
Would a solution as follows be appropriate?
in arch/arm/mach-omap2/Kconfig:
 config MACH_OMAP_ZOOM2
           bool "OMAP3 ZOOM2 board"
           depends on ARCH_OMAP3 && ARCH_OMAP34XX
+        select TWL4030_CORE if VIDEO_OMAP3
 
A similar strategy has been implemented for N800, albeit for other
peripherals.
Regards,
Nishanth Menon

  reply	other threads:[~2009-02-17  8:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  0:15 [OMAPZOOM][PATCH] Testing for TWL4030 in board file change Dominic Curran
2009-02-17  8:11 ` Nishanth Menon [this message]
2009-02-17 14:27   ` Curran, Dominic
2009-02-17 15:33     ` Nishanth Menon
2009-02-17 16:02       ` Aguirre Rodriguez, Sergio Alberto
2009-02-17 16:52         ` Nishanth Menon
2009-02-17 17:20           ` Aguirre Rodriguez, Sergio Alberto
2009-02-17 19:35         ` Curran, Dominic

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=499A7133.4050803@gmail.com \
    --to=menon.nishanth@gmail.com \
    --cc=dcurran@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@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