devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
	"'Sylwester Nawrocki'" <s.nawrocki@samsung.com>,
	"'Tomasz Figa'" <tomasz.figa@gmail.com>,
	"'Chanwoo Choi'" <cw00.choi@samsung.com>,
	"'Stephen Boyd'" <sboyd@kernel.org>,
	"'Michael Turquette'" <mturquette@baylibre.com>,
	"'Rob Herring'" <robh+dt@kernel.org>,
	"'Krzysztof Kozlowski'" <krzysztof.kozlowski+dt@linaro.org>
Cc: "'Alim Akhtar'" <alim.akhtar@samsung.com>,
	<linux-samsung-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 2/3] clk: samsung: exynosautov9: add missing gate clks for peric0/c1
Date: Tue, 28 Jun 2022 11:10:20 +0900	[thread overview]
Message-ID: <000301d88a94$37aa7320$a6ff5960$@samsung.com> (raw)
In-Reply-To: <6d7b0ea7-7918-aea4-6f2f-46d4870d92ad@linaro.org>

> Subject: Re: [PATCH 2/3] clk: samsung: exynosautov9: add missing gate clks
> for peric0/c1
> 
> On 27/06/2022 02:52, Chanho Park wrote:
> > "gout_peric0_pclk_1" and "gout_peric1_pclk_1" should be added to
> > peric0 and peric1 respectively.
> 
> Where is exactly the bug? The commit msg suggests that they were added to
> different block, but there is no code removal.

I thought they should be added from previous patch because clock IDs were existing without implementations.
I can drop fixes tags next patchset.

Best Regards,
Chanho Park


  reply	other threads:[~2022-06-28  2:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220627005413epcas2p3b3a22da2bf40b77b942cb2c6427135d5@epcas2p3.samsung.com>
2022-06-27  0:52 ` [PATCH 0/3] fixes for exynosautov9 clock Chanho Park
     [not found]   ` <CGME20220627005413epcas2p39750fb5876366881b8535ee516c1bebe@epcas2p3.samsung.com>
2022-06-27  0:52     ` [PATCH 1/3] dt-bindings: clock: exynosautov9: correct clock numbering of peric0/c1 Chanho Park
2022-06-27 11:33       ` Krzysztof Kozlowski
2022-06-28  2:15         ` Chanho Park
2022-06-28 10:02           ` Krzysztof Kozlowski
2022-07-04  7:32             ` Chanho Park
     [not found]   ` <CGME20220627005413epcas2p37d6b3cbea055cecade47ad304b40b7e3@epcas2p3.samsung.com>
2022-06-27  0:52     ` [PATCH 2/3] clk: samsung: exynosautov9: add missing gate clks for peric0/c1 Chanho Park
2022-06-27 11:30       ` Krzysztof Kozlowski
2022-06-28  2:10         ` Chanho Park [this message]
2022-06-28  6:58           ` Krzysztof Kozlowski
     [not found]   ` <CGME20220627005413epcas2p452229025b91f81ac86a4ddd403c64765@epcas2p4.samsung.com>
2022-06-27  0:52     ` [PATCH 3/3] clk: samsung: exynosautov9: correct register offsets of peric0/c1 Chanho Park
2022-06-27 11:31       ` Krzysztof Kozlowski

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='000301d88a94$37aa7320$a6ff5960$@samsung.com' \
    --to=chanho61.park@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=tomasz.figa@gmail.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;
as well as URLs for NNTP newsgroup(s).