From: Valentine <valentine.barshak@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] pinctrl: sh-pfc: pfc-r8a7790: Update VIN groups
Date: Tue, 10 Dec 2013 16:16:02 +0000 [thread overview]
Message-ID: <52A73E42.1080604@cogentembedded.com> (raw)
In-Reply-To: <1386690611-2014-1-git-send-email-valentine.barshak@cogentembedded.com>
On 12/10/2013 07:57 PM, Laurent Pinchart wrote:
> Hi Valentine,
>
> Thank you for the patches.
>
> On Tuesday 10 December 2013 19:50:09 Valentine Barshak wrote:
>> This adds missing VIN pins to the pfc-r8a7790 driver and reorganizes
>> the VIN groups to cover all possible configurations of VIN data pins.
>> This also groups hsync and vsync pins together and renames "field_signal"
>> and "data_enable" groups to "field" and "clkenb" respectively.
>>
>> Valentine Barshak (2):
>> pinctrl: sh-pfc: pfc-r8a7790: Add full VIN1/2/3 support
>> pinctrl: sh-pfc: pfc-r8a7790: Reorganize and rename VIN pin groups
>
> From a review point of view it would make my life much easier if you could
> switch the patches order. The reason is that patch 2/2 is currently pretty big
> because 1/2 comes first. Inverting them would make the reorganization patch
> simpler, and would make the VIN1/2/3 support patch cleaner.
Current layout splits pin addition and reorganization in 2 completely
separate steps.
Inverting will involve complete rework of the patches.
The reorganization patch would still be pretty big and it would have
to partially include VIN1-related changes from "Add full VIN1/2/3 support"
since some VIN1 pins are missing.
I'll probably try to switch and split them into more patches then.
>
>> drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 441 +++++++++++++++++++++++++++-----
>> 1 file changed, 382 insertions(+), 59 deletions(-)
>
Thanks,
Val.
prev parent reply other threads:[~2013-12-10 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:50 [PATCH 0/2] pinctrl: sh-pfc: pfc-r8a7790: Update VIN groups Valentine Barshak
2013-12-10 15:57 ` Laurent Pinchart
2013-12-10 16:16 ` 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=52A73E42.1080604@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 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.