From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Device Tree support for Picochip picoXcell
Date: Thu, 18 Aug 2011 17:02:02 +0100 [thread overview]
Message-ID: <20110818160202.GF2811@pulham.picochip.com> (raw)
In-Reply-To: <1312884661-27205-1-git-send-email-jamie@jamieiles.com>
On Tue, Aug 09, 2011 at 11:10:58AM +0100, Jamie Iles wrote:
> This series adds initial support for Picochip picoXcell devices. I've based
> this off of Grant's devicetree/test branch and also on top of Russell's GPIO
> includes cleanup.
>
> I have a second set of patches that add clk support but I've left them out for
> now to keep the changes to a minimum.
>
> Jamie Iles (3):
> picoxcell: support for Picochip picoxcell devices
> picoxcell: add the DTS for pc3x2 and pc3x3 devices
> picoxcell: add the DTS for the PC7302 board
Does anyone have any feedback on these? I've identified a couple of
changes for a v2, in particular using of_platform_populate rather than
of_platform_probe() and cleaning up some empty headers. I could also
take advantage of Russell's io.h cleanup and Marc's sched_clock() if
they get merged first.
Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Iles <jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
To: Jamie Iles <jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/3] Device Tree support for Picochip picoXcell
Date: Thu, 18 Aug 2011 17:02:02 +0100 [thread overview]
Message-ID: <20110818160202.GF2811@pulham.picochip.com> (raw)
In-Reply-To: <1312884661-27205-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
On Tue, Aug 09, 2011 at 11:10:58AM +0100, Jamie Iles wrote:
> This series adds initial support for Picochip picoXcell devices. I've based
> this off of Grant's devicetree/test branch and also on top of Russell's GPIO
> includes cleanup.
>
> I have a second set of patches that add clk support but I've left them out for
> now to keep the changes to a minimum.
>
> Jamie Iles (3):
> picoxcell: support for Picochip picoxcell devices
> picoxcell: add the DTS for pc3x2 and pc3x3 devices
> picoxcell: add the DTS for the PC7302 board
Does anyone have any feedback on these? I've identified a couple of
changes for a v2, in particular using of_platform_populate rather than
of_platform_probe() and cleaning up some empty headers. I could also
take advantage of Russell's io.h cleanup and Marc's sched_clock() if
they get merged first.
Jamie
next prev parent reply other threads:[~2011-08-18 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 10:10 [PATCH 0/3] Device Tree support for Picochip picoXcell Jamie Iles
2011-08-09 10:10 ` Jamie Iles
2011-08-09 10:10 ` [PATCH 1/3] picoxcell: support for Picochip picoxcell devices Jamie Iles
2011-08-09 10:10 ` Jamie Iles
2011-08-20 6:31 ` Grant Likely
2011-08-20 6:31 ` Grant Likely
2011-08-20 6:52 ` Jamie Iles
2011-08-20 6:52 ` Jamie Iles
2011-08-20 14:37 ` Grant Likely
2011-08-20 14:37 ` Grant Likely
2011-08-09 10:11 ` [PATCH 2/3] picoxcell: add the DTS for pc3x2 and pc3x3 devices Jamie Iles
2011-08-09 10:11 ` Jamie Iles
2011-08-09 10:11 ` [PATCH 3/3] picoxcell: add the DTS for the PC7302 board Jamie Iles
2011-08-09 10:11 ` Jamie Iles
2011-08-18 16:02 ` Jamie Iles [this message]
2011-08-18 16:02 ` [PATCH 0/3] Device Tree support for Picochip picoXcell Jamie Iles
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=20110818160202.GF2811@pulham.picochip.com \
--to=jamie@jamieiles.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.