All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
	linux-clk@vger.kernel.org
Cc: robh+dt@kernel.org, gregkh@linuxfoundation.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Subject: Re: [PATCH v14 4/5] clk: clocking-wizard: Fix the reconfig for 5.2
Date: Mon, 22 Aug 2022 19:03:54 -0700	[thread overview]
Message-ID: <20220823020356.561D0C433C1@smtp.kernel.org> (raw)
In-Reply-To: <20220411100443.15132-5-shubhrajyoti.datta@xilinx.com>

Quoting Shubhrajyoti Datta (2022-04-11 03:04:42)
> The 5.2 the reconfig is triggered by writing 7 followed by
> 2 to the reconfig reg. Add the same. Also 6.0 is backward
> compatible so it should be fine.
> 
> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
> ---

Applied to clk-next

  reply	other threads:[~2022-08-23  2:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 10:04 [PATCH v14 0/5] clk: clocking-wizard: Driver updates Shubhrajyoti Datta
2022-04-11 10:04 ` [PATCH v14 1/5] dt-bindings: add documentation of xilinx clocking wizard Shubhrajyoti Datta
2022-04-14  1:02   ` Rob Herring
2022-08-23  2:02   ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 2/5] clk: clocking-wizard: Move clocking-wizard out Shubhrajyoti Datta
2022-08-23  2:03   ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 3/5] clk: clocking-wizard: Rename nr-outputs to xlnx,nr-outputs Shubhrajyoti Datta
2022-08-23  2:03   ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 4/5] clk: clocking-wizard: Fix the reconfig for 5.2 Shubhrajyoti Datta
2022-08-23  2:03   ` Stephen Boyd [this message]
2022-04-11 10:04 ` [PATCH v14 5/5] clk: clocking-wizard: Update the compatible Shubhrajyoti Datta
2022-08-23  2:04   ` Stephen Boyd
2022-06-13  5:23 ` [PATCH v14 0/5] clk: clocking-wizard: Driver updates Shubhrajyoti Datta
2022-07-14 11:26 ` Michal Simek
2022-07-14 11:35   ` Greg Kroah-Hartman

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=20220823020356.561D0C433C1@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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 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.