From: Tony Lindgren <tony@atomide.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
sre@debian.org, sre@ring0.de,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, khilman@kernel.org,
aaro.koskinen@iki.fi, freemangordon@abv.bg,
bcousson@baylibre.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, sakari.ailus@iki.fi,
devicetree@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [RFC] adp1653: Add device tree bindings for LED controller
Date: Mon, 17 Nov 2014 07:06:17 -0800 [thread overview]
Message-ID: <20141117150617.GD7046@atomide.com> (raw)
In-Reply-To: <201411171601.32311@pali>
* Pali Rohár <pali.rohar@gmail.com> [141117 07:03]:
> On Monday 17 November 2014 15:55:46 Tony Lindgren wrote:
> >
> > There's nothing stopping us from initializing the camera code
> > from pdata-quirks.c for now to keep it working. Certainly the
> > binding should be added to the driver, but that removes a
> > dependency to the legacy booting mode if things are otherwise
> > working.
>
> Tony, legacy board code for n900 is not in mainline tree. And
> that omap3 camera subsystem for n900 is broken since 3.5
> kernel... (both Front and Back camera on n900 show only green
> picture).
I'm still seeing the legacy board code for n900 in mainline tree :)
It's deprecated, but still there.
Are you maybe talking about some other piece of platform_data that's
no longer in the mainline kernel?
No idea what might be wrong with the camera though.
Regards,
Tony
next prev parent reply other threads:[~2014-11-17 15:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 7:59 [RFC] adp1653: Add device tree bindings for LED controller Pavel Machek
2014-11-16 8:11 ` Lars-Peter Clausen
2014-11-16 8:43 ` Pavel Machek
2014-11-16 10:09 ` Andreas Färber
2014-11-16 10:15 ` Pavel Machek
2014-11-17 8:43 ` Pali Rohár
2014-11-17 10:05 ` Pavel Machek
2014-11-17 10:09 ` Pali Rohár
2014-11-17 10:15 ` Pavel Machek
2014-11-17 14:55 ` Tony Lindgren
2014-11-17 15:01 ` Pali Rohár
2014-11-17 15:04 ` Sakari Ailus
2014-11-17 15:15 ` Pali Rohár
2014-11-22 18:45 ` Ivaylo Dimitrov
2014-11-17 15:06 ` Tony Lindgren [this message]
2014-11-17 15:21 ` Pali Rohár
2014-11-18 18:35 ` Pavel Machek
2014-11-19 18:01 ` Sakari Ailus
2014-11-17 14:58 ` Sakari Ailus
2014-11-18 8:09 ` Jacek Anaszewski
2014-11-18 8:46 ` Pavel Machek
2014-11-18 10:04 ` Jacek Anaszewski
2014-11-18 11:32 ` Pavel Machek
2014-11-18 12:52 ` Jacek Anaszewski
2014-11-18 13:21 ` Pavel Machek
2014-11-18 16:02 ` Jacek Anaszewski
2014-11-18 16:51 ` Pavel Machek
2014-11-19 9:45 ` Jacek Anaszewski
2014-11-19 17:53 ` Sakari Ailus
2014-11-20 9:21 ` Jacek Anaszewski
2014-11-20 12:13 ` Pavel Machek
2014-11-20 12:12 ` Pavel Machek
2014-11-20 12:48 ` Jacek Anaszewski
2014-11-20 12:38 ` Jacek Anaszewski
2014-11-18 8:50 ` Pavel Machek
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=20141117150617.GD7046@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=freemangordon@abv.bg \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sre@debian.org \
--cc=sre@ring0.de \
/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).