devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>,
	Alexey Firago <alexey_firago@mentor.com>
Cc: mturquette@baylibre.com, robh+dt@kernel.org,
	geert@linux-m68k.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/3] clk: Add support for IDT 5P49V5935
Date: Fri, 7 Apr 2017 21:55:02 +0200	[thread overview]
Message-ID: <a0f2f6db-cbcb-084b-0533-216acd1b2d48@gmail.com> (raw)
In-Reply-To: <20170407194013.GD7065@codeaurora.org>

On 04/07/2017 09:40 PM, Stephen Boyd wrote:
> On 04/07, Alexey Firago wrote:
>> This series adds support for IDT VersaClock 5P49V5935 programmable clock
>> generator to the existing clk-versaclock5 driver. Driver is also updated to
>> simplify addition of support for more VersaClock 5 models. 
>>
>> Patches were verified on Avnet UltraZed-EG board with IO Carrier Card.
>>
>> Changes in V2:
>> - Introduce vc5_chip_info structure describing chip features
>> - Set vc5_chip_info for the supported chips using clk_vc5_of_match[].data
>> - Add 5P49V5935 support using vc5_chip_info approach
>> - Fix idx comparison in vc5_of_clk_get ('>' to '>=')
>>
>> Changes in V3:
>> - Change type of clk_fod_cnt and clk_out_cnt to unsigned int
>> - Add missed 'const' to vc5_chip_info instance declaration
>> - Use of_device_get_match_data() to initialize vc5_chip_info on probe 
>>
>> Changes in V4:
>> - Add 'const' to vc5_chip_info.flags
> 
> Could any Reviewed-by tags get carried over? I'll wait for Marek
> to resend them I guess.
> 
I'll review the patches ASAP

-- 
Best regards,
Marek Vasut

      reply	other threads:[~2017-04-07 19:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07  9:12 [PATCH v4 0/3] clk: Add support for IDT 5P49V5935 Alexey Firago
2017-04-07  9:12 ` [PATCH v4 1/3] clk: vc5: Add structure to describe particular chip features Alexey Firago
2017-04-07 19:55   ` Marek Vasut
     [not found]   ` <1491556344-9465-2-git-send-email-alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-04-19 16:09     ` Stephen Boyd
2017-04-07  9:12 ` [PATCH v4 3/3] clk: vc5: Add support for IDT VersaClock 5P49V5935 Alexey Firago
     [not found]   ` <1491556344-9465-4-git-send-email-alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-04-07 19:56     ` Marek Vasut
2017-04-19 16:09   ` Stephen Boyd
     [not found] ` <1491556344-9465-1-git-send-email-alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-04-07  9:12   ` [PATCH v4 2/3] clk: vc5: Add bindings " Alexey Firago
     [not found]     ` <1491556344-9465-3-git-send-email-alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-04-07 19:56       ` Marek Vasut
2017-04-10 20:10       ` Rob Herring
2017-04-19 16:09       ` Stephen Boyd
2017-04-07 19:40   ` [PATCH v4 0/3] clk: Add support for IDT 5P49V5935 Stephen Boyd
2017-04-07 19:55     ` Marek Vasut [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=a0f2f6db-cbcb-084b-0533-216acd1b2d48@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=alexey_firago@mentor.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.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).