All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "Sam Protsenko" <semen.protsenko@linaro.org>,
	"André Draszik" <andre.draszik@linaro.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Cc: peter.griffin@linaro.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com,
	willmcvicker@google.com, alim.akhtar@samsung.com,
	s.nawrocki@samsung.com, tomasz.figa@gmail.com,
	cw00.choi@samsung.com, mturquette@baylibre.com, sboyd@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: exynos: gs101: use correct clocks for usi8
Date: Mon, 29 Jan 2024 16:33:17 +0000	[thread overview]
Message-ID: <49d187f5-3c37-4c3b-a2f5-52dd805e84ee@linaro.org> (raw)
In-Reply-To: <b801e6b2-dfdf-4776-b90a-83780982b142@linaro.org>



On 1/27/24 04:00, Tudor Ambarus wrote:
>>> Wrong pclk clocks have been used in this usi8 instance here. For USI
>>> and I2C, we need the ipclk and pclk, where pclk is the bus clock.
>>> Without it, nothing can work.
>> Empty line is missing here?
>>
>>> It is unclear what exactly is using USI8_USI_CLK, but it is not
>>> required for the IP to be operational at this stage, while pclk is.
>> From [1] it looks like DIV_CLK_PERIC0_USI8_USI is a common parrent for
>> these two leaf gate clocks:
>>   1. GOUT_BLK_PERIC0_UID_RSTNSYNC_CLK_PERIC0_USI8_USI_IPCLKPORT_CLK
>>   2. GOUT_BLK_PERIC0_UID_PERIC0_TOP0_IPCLKPORT_IPCLK_7
>>
>> So IIUC, you replace clock #1 with clock #2 in this patch? If so, I
> No, GOUT_BLK_PERIC0_UID_PERIC0_TOP0_IPCLKPORT_IPCLK_7 is already used by
> IPCLK, the one that controls the clock frequency.
> 
> So I understand Andre' replaces a child of the USI8 with something else.
> 
> I don't think this works. We shall at least test it. I tested my usi8
> patches with the eeprom that's populated on the battery connector. I'll
> sync with Andre' offline and redo the tests on Monday.

Andre' is right, I messed up the bus clocks for USI. I tested the IPCLK,
the one that feeds USI clients, but I failed to correctly test the bus
clock. I retested by removing the clk_ignore_unused bootargs param and
verified that the patch is correct.

Reviewed-by: Tudor Ambarus <tudor.ambarus@linaro.org>
Tested-by: Tudor Ambarus <tudor.ambarus@linaro.org>

WARNING: multiple messages have this Message-ID (diff)
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "Sam Protsenko" <semen.protsenko@linaro.org>,
	"André Draszik" <andre.draszik@linaro.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Cc: peter.griffin@linaro.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com,
	willmcvicker@google.com, alim.akhtar@samsung.com,
	s.nawrocki@samsung.com, tomasz.figa@gmail.com,
	cw00.choi@samsung.com, mturquette@baylibre.com, sboyd@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: exynos: gs101: use correct clocks for usi8
Date: Mon, 29 Jan 2024 16:33:17 +0000	[thread overview]
Message-ID: <49d187f5-3c37-4c3b-a2f5-52dd805e84ee@linaro.org> (raw)
In-Reply-To: <b801e6b2-dfdf-4776-b90a-83780982b142@linaro.org>



On 1/27/24 04:00, Tudor Ambarus wrote:
>>> Wrong pclk clocks have been used in this usi8 instance here. For USI
>>> and I2C, we need the ipclk and pclk, where pclk is the bus clock.
>>> Without it, nothing can work.
>> Empty line is missing here?
>>
>>> It is unclear what exactly is using USI8_USI_CLK, but it is not
>>> required for the IP to be operational at this stage, while pclk is.
>> From [1] it looks like DIV_CLK_PERIC0_USI8_USI is a common parrent for
>> these two leaf gate clocks:
>>   1. GOUT_BLK_PERIC0_UID_RSTNSYNC_CLK_PERIC0_USI8_USI_IPCLKPORT_CLK
>>   2. GOUT_BLK_PERIC0_UID_PERIC0_TOP0_IPCLKPORT_IPCLK_7
>>
>> So IIUC, you replace clock #1 with clock #2 in this patch? If so, I
> No, GOUT_BLK_PERIC0_UID_PERIC0_TOP0_IPCLKPORT_IPCLK_7 is already used by
> IPCLK, the one that controls the clock frequency.
> 
> So I understand Andre' replaces a child of the USI8 with something else.
> 
> I don't think this works. We shall at least test it. I tested my usi8
> patches with the eeprom that's populated on the battery connector. I'll
> sync with Andre' offline and redo the tests on Monday.

Andre' is right, I messed up the bus clocks for USI. I tested the IPCLK,
the one that feeds USI clients, but I failed to correctly test the bus
clock. I retested by removing the clk_ignore_unused bootargs param and
verified that the patch is correct.

Reviewed-by: Tudor Ambarus <tudor.ambarus@linaro.org>
Tested-by: Tudor Ambarus <tudor.ambarus@linaro.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-01-29 16:33 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27  0:35 gs101 oriole: peripheral block 0 (peric0) fixes André Draszik
2024-01-27  0:35 ` André Draszik
2024-01-27  0:35 ` [PATCH 1/5] clk: samsung: gs101: gpio_peric0_pclk needs to be kept on André Draszik
2024-01-27  0:35   ` André Draszik
2024-01-27  3:06   ` Sam Protsenko
2024-01-27  3:06     ` Sam Protsenko
2024-01-27  3:51   ` Tudor Ambarus
2024-01-27  3:51     ` Tudor Ambarus
2024-01-29 12:54   ` Peter Griffin
2024-01-29 12:54     ` Peter Griffin
2024-01-27  0:35 ` [PATCH 2/5] arm64: dts: exynos: gs101: fix usi8 default mode André Draszik
2024-01-27  0:35   ` André Draszik
2024-01-27  3:05   ` Sam Protsenko
2024-01-27  3:05     ` Sam Protsenko
2024-01-27  3:48   ` Tudor Ambarus
2024-01-27  3:48     ` Tudor Ambarus
2024-01-29  9:48   ` Peter Griffin
2024-01-29  9:48     ` Peter Griffin
2024-01-27  0:35 ` [PATCH 3/5] arm64: dts: exynos: gs101: use correct clocks for usi8 André Draszik
2024-01-27  0:35   ` André Draszik
2024-01-27  3:22   ` Sam Protsenko
2024-01-27  3:22     ` Sam Protsenko
2024-01-27  4:00     ` Tudor Ambarus
2024-01-27  4:00       ` Tudor Ambarus
2024-01-29 16:33       ` Tudor Ambarus [this message]
2024-01-29 16:33         ` Tudor Ambarus
2024-01-29 14:01     ` André Draszik
2024-01-29 14:01       ` André Draszik
2024-01-27  0:35 ` [PATCH 4/5] arm64: dts: exynos: gs101: use correct clocks for usi_uart André Draszik
2024-01-27  0:35   ` André Draszik
2024-01-27  1:37   ` André Draszik
2024-01-27  1:37     ` André Draszik
2024-01-27  3:23   ` Sam Protsenko
2024-01-27  3:23     ` Sam Protsenko
2024-01-27  4:03   ` Tudor Ambarus
2024-01-27  4:03     ` Tudor Ambarus
2024-01-29 16:39     ` Tudor Ambarus
2024-01-29 16:39       ` Tudor Ambarus
2024-01-27  0:35 ` [PATCH 5/5] clk: samsung: gs101: don't mark non-essential clocks as critical André Draszik
2024-01-27  0:35   ` André Draszik
2024-01-27  1:38   ` André Draszik
2024-01-27  1:38     ` André Draszik
2024-01-27  3:30   ` Sam Protsenko
2024-01-27  3:30     ` Sam Protsenko
2024-01-29 14:37     ` André Draszik
2024-01-29 14:37       ` André Draszik
2024-01-29 19:16       ` Sam Protsenko
2024-01-29 19:16         ` Sam Protsenko
2024-01-30  9:31         ` André Draszik
2024-01-30  9:31           ` André Draszik
2024-01-30  9:39           ` Tudor Ambarus
2024-01-30  9:39             ` Tudor Ambarus
2024-01-29 16:44   ` Tudor Ambarus
2024-01-29 16:44     ` Tudor Ambarus
2024-01-27  3:01 ` gs101 oriole: peripheral block 0 (peric0) fixes Sam Protsenko
2024-01-27  3:01   ` Sam Protsenko

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=49d187f5-3c37-4c3b-a2f5-52dd805e84ee@linaro.org \
    --to=tudor.ambarus@linaro.org \
    --cc=alim.akhtar@samsung.com \
    --cc=andre.draszik@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel-team@android.com \
    --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-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=peter.griffin@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=tomasz.figa@gmail.com \
    --cc=willmcvicker@google.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.