Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH 7/7] memory: tegra: Rework update_clock_tree_delay()
Date: Thu, 18 Apr 2024 19:19:26 +0200	[thread overview]
Message-ID: <58fb33a6-59b9-46f9-b836-917f6f40da27@linaro.org> (raw)
In-Reply-To: <tohunkhyf4ojukj4sjmjn4wfxzv6jdxvngma6f73tztbedvy62@6x3unhxhvmdl>

On 15/04/2024 13:22, Diogo Ivo wrote:
> On Sat, Apr 13, 2024 at 10:08:40AM +0200, Krzysztof Kozlowski wrote:
>> On 09/04/2024 11:46, Diogo Ivo wrote:
>>> Further streamline this function by moving the delay post-processing
>>> to the callers, leaving it only with the task of returing the measured
>>> delay values.
>>>
>>> Signed-off-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
>>> ---
>>>  drivers/memory/tegra/tegra210-emc-cc-r21021.c | 120 +++++++-----------
>>>  1 file changed, 46 insertions(+), 74 deletions(-)
>>>
>>> diff --git a/drivers/memory/tegra/tegra210-emc-cc-r21021.c b/drivers/memory/tegra/tegra210-emc-cc-r21021.c
>>> index ec2f84758d55..5e2c84fc835c 100644
>>> --- a/drivers/memory/tegra/tegra210-emc-cc-r21021.c
>>> +++ b/drivers/memory/tegra/tegra210-emc-cc-r21021.c
>>> @@ -105,7 +105,7 @@ enum {
>>>  			  next->ptfv_list[w])) /			\
>>>  			(next->ptfv_list[w] + 1);			\
>>>  									\
>>> -		emc_dbg(emc, EMA_UPDATES, "%s: (s=%lu) EMA: %u\n",	\
>>> +		emc_dbg(emc, EMA_UPDATES, "%s: (s=%u) EMA: %u\n",	\
>>
>> Does not look related.
> 
> This was necessary to avoid compiler warnings as before when we were calling
> this macro from update_clock_tree_delay() the value we were passing in was
> declared as an unsigned long and now it is declared as u32, which it still
> big enough for the values we are dealing with here.

OK, that's difficult to see from the patch context but looks right.

Best regards,
Krzysztof


      reply	other threads:[~2024-04-18 17:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  9:46 [PATCH 0/7] Cleanup Tegra210 EMC frequency scaling Diogo Ivo
2024-04-09  9:46 ` [PATCH 1/7] memory: tegra: Remove periodic compensation duplicate calls Diogo Ivo
2024-04-09  9:46 ` [PATCH 2/7] memory: tegra: Move DQSOSC measurement to common place Diogo Ivo
2024-04-09  9:46 ` [PATCH 3/7] memory: tegra: Reword and correct comments Diogo Ivo
2024-04-09  9:46 ` [PATCH 4/7] memory: tegra: Change macros to interpret parameter as integer Diogo Ivo
2024-04-13  8:02   ` Krzysztof Kozlowski
2024-04-15 11:07     ` Diogo Ivo
2024-04-09  9:46 ` [PATCH 5/7] memory: tegra: Loop update_clock_tree_delay() Diogo Ivo
2024-04-09  9:46 ` [PATCH 6/7] memory: tegra: Move compare/update current delay values to a function Diogo Ivo
2024-04-13  8:07   ` Krzysztof Kozlowski
2024-04-15 11:17     ` Diogo Ivo
2024-04-09  9:46 ` [PATCH 7/7] memory: tegra: Rework update_clock_tree_delay() Diogo Ivo
2024-04-13  8:08   ` Krzysztof Kozlowski
2024-04-15 11:22     ` Diogo Ivo
2024-04-18 17:19       ` Krzysztof Kozlowski [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=58fb33a6-59b9-46f9-b836-917f6f40da27@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@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