From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM : i.MX27 : split code for allocation of ressources of camera and eMMA
Date: Tue, 11 Sep 2012 13:17:38 +0200 [thread overview]
Message-ID: <20120911111738.GU18243@pengutronix.de> (raw)
In-Reply-To: <CACKLOr11UbRF3cyKZ5p_9K81=KS=AQxQNZv1YmxtC0kJeoz1+g@mail.gmail.com>
On Tue, Sep 11, 2012 at 01:13:03PM +0200, javier Martin wrote:
> Hi,
>
> On 11 September 2012 11:47, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > Hi Javier,
> >
> > Since you worked in this area recently, can I have your Ack on this?
>
> Acked-by: Javier Martin <javier.martin@vista-silicon.com>
Thanks
>
> > As a side note: Please be prepared that all this should be removed in
> > the not-so-far future. It would be good if you start converting your
> > boards to devicetree soon. You may be doing so internally already, I
> > don't know.
>
> We made some tests regarding devicetree this summer but we found that
> there are some things missing yet:
> - pinctrl
> - soc-camera and video sensor
>
> I don't know if people from Linaro is planning to deal with pinctrl
> for i.MX27 or not.
I don't think Linaro will do anything for the older i.MX like the
i.MX27. With soc-camera I'm optimistic that someone will come up
with patches soon.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-09-11 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 11:06 [PATCH v2] ARM : i.MX27 : split code for allocation of ressources of camera and eMMA Gaëtan Carlier
2012-09-11 9:47 ` Sascha Hauer
2012-09-11 11:13 ` javier Martin
2012-09-11 11:17 ` Sascha Hauer [this message]
2012-10-09 13:01 ` Gaëtan Carlier
2012-10-10 8:34 ` Sascha Hauer
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=20120911111738.GU18243@pengutronix.de \
--to=s.hauer@pengutronix.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;
as well as URLs for NNTP newsgroup(s).