From: valentin.longchamp@epfl.ch (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] mx31moboard: patches for next merge window
Date: Fri, 16 Oct 2009 11:02:58 +0200 [thread overview]
Message-ID: <4AD836C2.7070707@epfl.ch> (raw)
In-Reply-To: <20091016081722.GB7208@pengutronix.de>
Uwe Kleine-K?nig wrote:
> On Thu, Oct 15, 2009 at 11:42:54AM +0200, Valentin Longchamp wrote:
>> Here are the patches I would like to push during the next merge window for
>> the mx31moboard platform.
>>
>> It consists of a fix for a small hardware design issue for the main serial
>> port, a few GPIOs used on the robots that are declared, camera support and
>> finally MC13783 support as it is now getting ready.
>>
>> For MC13783, we would need RTC as well, but I did not add it yet since it
>> is not in mainline yet.
> Note I'm currently overhauling mc13783-core.c resulting in an API change.
>
> I plan to add some compatibility stuff, but I'll let you know when I'm
> done anyhow. Are you interested in testing my changes?
Sure. Tell me when you have something and I will give them a spin on the
robot.
>
> I don't know yet if I will try to get the rtc-support into mainline, but
> Sasche posted a patch (without feedback) some time ago. (It's only a
> minimal driver, no alarm, no reset detection.)
>
That would be nice. We only rely on this MC13783 RTC, so if we can get
it into mainline it would be great for us.
Another thing is the RGB led support. We have two of these leds on our
robot. Is anyone else using them ? Has someone already worked on them ?
The support should not be very hard to add now that we have MC13783 core
support and since there is a LED class. The only API change to led would
be to add RGB support, which is not present now. Any comments on this ?
Best Regards
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp at epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
next prev parent reply other threads:[~2009-10-16 9:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 9:42 [RFC] mx31moboard: patches for next merge window Valentin Longchamp
2009-10-15 9:42 ` [PATCH 1/6] mx31: various pins used for mx31moboard Valentin Longchamp
2009-10-15 9:42 ` [PATCH 2/6] mx31moboard: serial port fix Valentin Longchamp
2009-10-15 9:42 ` [PATCH 3/6] mx31moboard: support for pin linked for battery presence check Valentin Longchamp
2009-10-15 9:42 ` [PATCH 4/6] mx31moboard: initialize ipu device for all the boards Valentin Longchamp
2009-10-15 9:42 ` [PATCH 5/6] mx31moboard: camera support Valentin Longchamp
2009-10-15 9:43 ` [PATCH 6/6] mx31moboard: SPI and MC13783 votage regulator support Valentin Longchamp
2009-10-16 8:18 ` Uwe Kleine-König
2009-10-16 18:35 ` [PATCH 5/6] mx31moboard: camera support Russell King - ARM Linux
2009-10-16 21:09 ` Guennadi Liakhovetski
2009-10-19 16:41 ` Valentin Longchamp
2009-10-20 8:09 ` Sascha Hauer
2009-10-21 17:11 ` Valentin Longchamp
2009-10-23 23:45 ` Guennadi Liakhovetski
2009-10-28 14:32 ` Valentin Longchamp
2009-11-03 11:31 ` Valentin Longchamp
2009-11-04 18:22 ` Guennadi Liakhovetski
2009-11-04 21:37 ` Valentin Longchamp
2009-10-23 22:56 ` Guennadi Liakhovetski
2009-10-28 14:36 ` Valentin Longchamp
2009-10-15 22:14 ` [RFC] mx31moboard: patches for next merge window Sascha Hauer
2009-10-16 8:17 ` Uwe Kleine-König
2009-10-16 9:02 ` Valentin Longchamp [this message]
2009-10-24 8:25 ` Uwe Kleine-König
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=4AD836C2.7070707@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--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).