From: Valentine <valentine.barshak@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH V3 0/3] ARM: shmobile: koelsch: Add VIN1 camera support
Date: Mon, 06 Jan 2014 13:53:15 +0000 [thread overview]
Message-ID: <52CAB54B.6050607@cogentembedded.com> (raw)
In-Reply-To: <1388145471-9361-1-git-send-email-valentine.barshak@cogentembedded.com>
On 01/06/2014 11:53 AM, Simon Horman wrote:
> On Fri, Dec 27, 2013 at 03:57:48PM +0400, Valentine Barshak wrote:
>> This adds VIN pins and clocks to R8A7791 SoC along with
>> VIN1 camera support to Koelsch board.
>>
>> This is probably a bit early since it depends on
>> the following pending patches:
>> http://marc.info/?l=linux-sh&m\x138807191506999&w=2
>> ([PATCH V2] media: soc_camera: rcar_vin: Add preliminary R-Car M2 support)
>> http://marc.info/?l=linux-sh&m\x138814366919427&w=2
>> ([PATCH 0/3 V2] ARM: shmobile: koelsch: Add I2C support)
>>
>> Changes in V2:
>> * made koelsch_add_vin_device function static.
>>
>> Changes in V3:
>> * capitalized ARM in the subject.
>>
>> Valentine Barshak (3):
>> pinctrl: sh-pfc: r8a7791: Add VIN pins
>
> Laurent has queued this up.
>
>> ARM: shmobile: r8a7791: Add VIN clocks
>
> I will queue this up.
>
>> ARM: shmobile: koelsch: Add VIN1 SoC camera support
>
> Please repost this once the dependencies are present in either
> an rc release or my devel branch. Please also include a patch
> to update the koelsch defconfig to enable VIN.
>
OK, thanks!
Thanks,
Val.
>> arch/arm/mach-shmobile/board-koelsch.c | 76 +++++++
>> arch/arm/mach-shmobile/clock-r8a7791.c | 10 +
>> drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 360 +++++++++++++++++++++++++++++++++
>> 3 files changed, 446 insertions(+)
>>
>> --
>> 1.8.3.1
>>
prev parent reply other threads:[~2014-01-06 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 11:57 [PATCH V3 0/3] ARM: shmobile: koelsch: Add VIN1 camera support Valentine Barshak
2014-01-06 7:53 ` Simon Horman
2014-01-06 13:53 ` Valentine [this message]
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=52CAB54B.6050607@cogentembedded.com \
--to=valentine.barshak@cogentembedded.com \
--cc=linux-sh@vger.kernel.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).