linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: linux-clk <linux-clk@vger.kernel.org>
Cc: Adam Ford-BE <aford@beaconembedded.com>,
	Charles Stevens <charles.stevens@logicpd.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Marek Vasut <marek.vasut@gmail.com>,
	devicetree <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] clk: vc5: Add support for IDT VersaClock 5P49V6965
Date: Sat, 2 May 2020 05:53:22 -0500	[thread overview]
Message-ID: <CAHCN7xJBxaS-7e=PY8BXVyit-Ye22JKmfOk3=oUTv1BZurE4oA@mail.gmail.com> (raw)
In-Reply-To: <20200404161537.2312297-1-aford173@gmail.com>

On Sat, Apr 4, 2020 at 11:15 AM Adam Ford <aford173@gmail.com> wrote:
>
> Update IDT VersaClock 5 driver to support 5P49V6965.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
>

Gentle ping.   Rob H has given the 2nd which adds the bindings his
'signed-of-by'

Once this has been approved, I'll be issuing an update to an another
patch series for this same clock, and once those have been approved,
I'll be introducing a new board, but I need this patch approved before
I can do that.

thanks,

adam

> diff --git a/drivers/clk/clk-versaclock5.c b/drivers/clk/clk-versaclock5.c
>
> index 24fef51fbcb5..fa96659f8023
> --- a/drivers/clk/clk-versaclock5.c
> +++ b/drivers/clk/clk-versaclock5.c
> @@ -124,6 +124,7 @@ enum vc5_model {
>         IDT_VC5_5P49V5933,
>         IDT_VC5_5P49V5935,
>         IDT_VC6_5P49V6901,
> +       IDT_VC6_5P49V6965,
>  };
>
>  /* Structure to describe features of a particular VC5 model */
> @@ -683,6 +684,7 @@ static int vc5_map_index_to_output(const enum vc5_model model,
>         case IDT_VC5_5P49V5925:
>         case IDT_VC5_5P49V5935:
>         case IDT_VC6_5P49V6901:
> +       case IDT_VC6_5P49V6965:
>         default:
>                 return n;
>         }
> @@ -956,12 +958,20 @@ static const struct vc5_chip_info idt_5p49v6901_info = {
>         .flags = VC5_HAS_PFD_FREQ_DBL,
>  };
>
> +static const struct vc5_chip_info idt_5p49v6965_info = {
> +       .model = IDT_VC6_5P49V6965,
> +       .clk_fod_cnt = 4,
> +       .clk_out_cnt = 5,
> +       .flags = 0,
> +};
> +
>  static const struct i2c_device_id vc5_id[] = {
>         { "5p49v5923", .driver_data = IDT_VC5_5P49V5923 },
>         { "5p49v5925", .driver_data = IDT_VC5_5P49V5925 },
>         { "5p49v5933", .driver_data = IDT_VC5_5P49V5933 },
>         { "5p49v5935", .driver_data = IDT_VC5_5P49V5935 },
>         { "5p49v6901", .driver_data = IDT_VC6_5P49V6901 },
> +       { "5p49v6965", .driver_data = IDT_VC6_5P49V6965 },
>         { }
>  };
>  MODULE_DEVICE_TABLE(i2c, vc5_id);
> @@ -972,6 +982,7 @@ static const struct of_device_id clk_vc5_of_match[] = {
>         { .compatible = "idt,5p49v5933", .data = &idt_5p49v5933_info },
>         { .compatible = "idt,5p49v5935", .data = &idt_5p49v5935_info },
>         { .compatible = "idt,5p49v6901", .data = &idt_5p49v6901_info },
> +       { .compatible = "idt,5p49v6965", .data = &idt_5p49v6965_info },
>         { },
>  };
>  MODULE_DEVICE_TABLE(of, clk_vc5_of_match);
> --
> 2.25.1
>

  parent reply	other threads:[~2020-05-02 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 16:15 [PATCH 1/2] clk: vc5: Add support for IDT VersaClock 5P49V6965 Adam Ford
2020-04-04 16:15 ` [PATCH 2/2] dt: Add bindings for IDT VersaClock 5P49V5925 Adam Ford
2020-04-14 18:15   ` Rob Herring
2020-05-29  4:05   ` Stephen Boyd
2020-05-02 10:53 ` Adam Ford [this message]
2020-05-29  4:04 ` [PATCH 1/2] clk: vc5: Add support for IDT VersaClock 5P49V6965 Stephen Boyd

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='CAHCN7xJBxaS-7e=PY8BXVyit-Ye22JKmfOk3=oUTv1BZurE4oA@mail.gmail.com' \
    --to=aford173@gmail.com \
    --cc=aford@beaconembedded.com \
    --cc=charles.stevens@logicpd.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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).