public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Cc: <linux-clk@vger.kernel.org>, <devel@driverdev.osuosl.org>,
	<devicetree@vger.kernel.org>, <sboyd@kernel.org>,
	<gregkh@linuxfoundation.org>, <mturquette@baylibre.com>,
	<git@xilinx.com>
Subject: Re: [PATCH v7 0/7] clk: clk-wizard: clock-wizard: Driver updates
Date: Fri, 12 Feb 2021 15:20:00 +0100	[thread overview]
Message-ID: <ed0d242b-203f-6166-95a3-1e9fe45bb689@xilinx.com> (raw)
In-Reply-To: <20210121153947.04da6fc1@xps13>

Hi Miquel,

On 1/21/21 3:39 PM, Miquel Raynal wrote:
> Hi Shubhrajyoti,
> 
> Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com> wrote on Wed, 4 Nov
> 2020 20:36:40 +0530:
> 
>> In the thread [1] Greg suggested that we move the driver
>> to the clk from the staging.
>> Add patches to address the concerns regarding the fractional and
>> set rate support in the TODO.
>>
>> The patch set does the following
>> - Trivial fixes for kernel doc.
>> - Move the driver to the clk folder
>> - Add capability to set rate.
>> - Add fractional support.
>> - Add support for configurable outputs.
>> - Make the output names unique so that multiple instances
>> do not crib.
> 
> Can someone tell me the status of this series? I think it would
> benefit everyone to have this driver "officially" supported in the
> main tree, unless there are crucial issues; in this case it might be
> good to know which ones?

v8 was sent here.

https://lore.kernel.org/r/1612446810-6113-1-git-send-email-shubhrajyoti.datta@xilinx.com

Unfortunately v9 is required.
Shubhrajyoti: Can you please keep Miquel in CC on v9?

Thanks,
Michal

      reply	other threads:[~2021-02-12 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 15:06 [PATCH v7 0/7] clk: clk-wizard: clock-wizard: Driver updates Shubhrajyoti Datta
2020-11-04 15:06 ` [PATCH v7 1/7] dt-bindings: add documentation of xilinx clocking wizard Shubhrajyoti Datta
2020-11-04 19:11   ` Rob Herring
2020-11-04 19:15   ` Rob Herring
2020-11-04 15:06 ` [PATCH v7 2/7] clk: clock-wizard: Add the clockwizard to clk directory Shubhrajyoti Datta
2020-11-04 15:06 ` [PATCH v7 3/7] clk: clock-wizard: Fix kernel-doc warning Shubhrajyoti Datta
2020-11-04 15:06 ` [PATCH v7 4/7] clk: clock-wizard: Add support for dynamic reconfiguration Shubhrajyoti Datta
2020-11-04 15:06 ` [PATCH v7 5/7] clk: clock-wizard: Add support for fractional support Shubhrajyoti Datta
2020-11-04 15:06 ` [PATCH v7 6/7] clk: clock-wizard: Remove the hardcoding of the clock outputs Shubhrajyoti Datta
2020-11-04 15:06 ` [PATCH v7 7/7] clk: clock-wizard: Update the fixed factor divisors Shubhrajyoti Datta
2020-12-13  5:36 ` [PATCH v7 0/7] clk: clk-wizard: clock-wizard: Driver updates Stephen Boyd
2021-01-21 14:40   ` Michal Simek
2020-12-15  9:13 ` Michal Simek
2020-12-15 19:10   ` Stephen Boyd
2021-01-21 14:39 ` Miquel Raynal
2021-02-12 14:20   ` Michal Simek [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=ed0d242b-203f-6166-95a3-1e9fe45bb689@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=shubhrajyoti.datta@xilinx.com \
    /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