linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: devices and boards files update for 3.3
Date: Fri, 16 Dec 2011 17:37:49 +0100	[thread overview]
Message-ID: <4EEB73DD.3070505@atmel.com> (raw)
In-Reply-To: <CAOesGMiEg-8LA9-yUXRrDwGLGfVeFn7Xax9jhkDr+fZ5GU06QA@mail.gmail.com>

On 12/16/2011 08:06 AM, Olof Johansson :
> Hi,
> 
> On Thu, Dec 15, 2011 at 6:25 AM, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>> Arnd, Olof,
>>
>> This pull request adds the ISI to the sam9m10g45 board. As ISI has
>> been waited for a long time on AT91, I think it is not possible to wait
>> for the DT support. Moreover, DT support for this camera sensor + ISI
>> soc interface seems not so trivial and will certainly need a handful of
>> kernel releases before being stabilized.
>> Other changes are quite simple and self-explanatory...
>>
>> The following changes since commit dc47ce90c3a822cd7c9e9339fe4d5f61dcb26b50:
>>
>>  Linux 3.2-rc5 (2011-12-09 15:09:32 -0800)
>>
>> are available in the git repository at:
>>  git://github.com/at91linux/linux-at91.git for-arnd-3.3-device_board
> 
> Sure, since you removed a defconfig I'm OK with a small amount of
> board addition for ISI.
> 
> However, I noticed that it doesn't build with at91sam9g45_defconfig:
> 
> arch/arm/mach-at91/board-sam9m10g45ek.c:195: error: unknown field
> 'full_mode' specified in initializer
> arch/arm/mach-at91/board-sam9m10g45ek.c:195: warning: excess elements
> in struct initializer
> arch/arm/mach-at91/board-sam9m10g45ek.c:195: warning: (near
> initialization for 'isi_data')
> arch/arm/mach-at91/board-sam9m10g45ek.c:198: error: unknown field
> 'mck_hz' specified in initializer
>
> Please fixup and send fresh request.

Olof,

Yes, this ISI driver addition is also dependent on an update of the ISI
driver itself that will certainly be included in 3.3 by Guennadi using
v4L2 path.

So, do we have to wait for its inclusion in linux-next or maybe we can
manage this little out-of-sync situation during the 3.3 life cycle...

ISI is a "several times reworked" and "long-awaited" driver and I really
would like to see it included in mainline soon...

Best regards,
-- 
Nicolas Ferre

  reply	other threads:[~2011-12-16 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 14:25 [GIT PULL] at91: devices and boards files update for 3.3 Nicolas Ferre
2011-12-16  7:06 ` Olof Johansson
2011-12-16 16:37   ` Nicolas Ferre [this message]
2011-12-16 21:03     ` Olof Johansson
2011-12-17 18:34       ` Guennadi Liakhovetski
2011-12-17 23:42         ` Olof Johansson
2011-12-18  0:08           ` Guennadi Liakhovetski
2011-12-20  4:32             ` Olof Johansson
2012-01-03 10:49               ` Nicolas Ferre
2012-01-03 10:59                 ` Guennadi Liakhovetski
2012-01-05 16:55               ` [PATCH 1/2 v3] V4L: atmel-isi: add code to enable/disable ISI_MCK clock Guennadi Liakhovetski
2012-01-05 17:09                 ` Russell King - ARM Linux
2012-01-05 17:15                   ` Nicolas Ferre
2012-01-05 17:21                     ` Guennadi Liakhovetski
2012-01-06  5:49                       ` Wu, Josh
     [not found] ` <4F02E1B9.30009@atmel.com>
2012-01-03 21:39   ` [GIT PULL v2] at91: devices and boards files update for 3.3 Arnd Bergmann
2012-01-04  9:20     ` Nicolas Ferre

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=4EEB73DD.3070505@atmel.com \
    --to=nicolas.ferre@atmel.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 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).