linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Taniya Das <tdas@codeaurora.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Add support for duty-cycle for RCG
Date: Thu, 29 Apr 2021 19:21:11 -0700	[thread overview]
Message-ID: <161974927117.177949.8019204674384480875@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <ed64fe46-361b-5bf9-88a6-d35cac2c98e7@codeaurora.org>

Quoting Taniya Das (2021-04-28 23:55:16)
> Thank you for your review.
> 
> On 4/28/2021 5:49 AM, Stephen Boyd wrote:
> > Quoting Taniya Das (2021-04-25 00:08:21)
> >> The root clock generators with MND divider has the capability to support
> >> change in duty-cycle by updating the 'D'. Add the clock ops which would
> >> check all the boundary conditions and enable setting the desired duty-cycle
> >> as per the consumer.
> >>
> >> [v3]
> >>    * Implement clockops for get_duty_cycle.
> >>    * Return -EINVAL for Non-MND or HID RCGs.
> > 
> > We don't need cover letters for single patches. Please add these details
> > after the dash before the diffstat on the single patch.
> > 
> 
> Sure Stephen, will take care from next time. Let me know in case I need 
> to re-submit the patch again.
> 

Don't think so. Merge window is open so I'll apply it in another week.

      reply	other threads:[~2021-04-30  2:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  7:08 [PATCH v3] Add support for duty-cycle for RCG Taniya Das
2021-04-25  7:08 ` [PATCH v3] clk: qcom: clk-rcg2: " Taniya Das
2021-05-26  3:36   ` Stephen Boyd
2021-04-28  0:19 ` [PATCH v3] " Stephen Boyd
2021-04-29  6:55   ` Taniya Das
2021-04-30  2:21     ` Stephen Boyd [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=161974927117.177949.8019204674384480875@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rnayak@codeaurora.org \
    --cc=tdas@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).