From: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
To: krzysztof.kozlowski@linaro.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-tegra@vger.kernel.org
Cc: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Subject: [PATCH v2 0/7] Cleanup Tegra210 EMC frequency scaling
Date: Fri, 19 Apr 2024 11:45:08 +0100 [thread overview]
Message-ID: <20240419104516.308975-1-diogo.ivo@tecnico.ulisboa.pt> (raw)
Hello,
This patch series consists of a general cleanup of the Tegra210 EMC
frequency scaling code for revision 7.
Currently the code is relying heavily on a function, update_clock_tree_delay(),
that is responsible for too many things, making it long and confusing.
The general idea with these patches is to simplify this function and its
surrounding code, making it more modular.
The motivation behind these changes (besides improving readability and
maintainability) is to make it simpler to add support in the future for
frequency change revisions other than 7, where we can reuse a large
portion of the modularized code rather than essentially repeating 2k
lines of code with minimal changes.
There are no functional changes with this patch set, as it is only meant
as preparation for following patches where revision 6 support is added.
The first version of the series can be found in [1]. The changes made in v2
are described in each patch.
[1]: https://lore.kernel.org/linux-tegra/20240409094632.62916-1-diogo.ivo@tecnico.ulisboa.pt/
Diogo Ivo (7):
memory: tegra: Remove periodic compensation duplicate calls
memory: tegra: Move DQSOSC measurement to common place
memory: tegra: Reword and correct comments
memory: tegra: Change macros to interpret parameter as integer
memory: tegra: Loop update_clock_tree_delay()
memory: tegra: Move compare/update current delay values to a function
memory: tegra: Rework update_clock_tree_delay()
drivers/memory/tegra/tegra210-emc-cc-r21021.c | 427 ++++--------------
1 file changed, 84 insertions(+), 343 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-19 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 10:45 Diogo Ivo [this message]
2024-04-19 10:45 ` [PATCH v2 1/7] memory: tegra: Remove periodic compensation duplicate calls Diogo Ivo
2024-04-19 10:45 ` [PATCH v2 2/7] memory: tegra: Move DQSOSC measurement to common place Diogo Ivo
2024-04-19 10:45 ` [PATCH v2 3/7] memory: tegra: Reword and correct comments Diogo Ivo
2024-04-19 10:45 ` [PATCH v2 4/7] memory: tegra: Change macros to interpret parameter as integer Diogo Ivo
2024-04-19 10:45 ` [PATCH v2 5/7] memory: tegra: Loop update_clock_tree_delay() Diogo Ivo
2024-04-19 10:45 ` [PATCH v2 6/7] memory: tegra: Move compare/update current delay values to a function Diogo Ivo
2024-04-19 10:45 ` [PATCH v2 7/7] memory: tegra: Rework update_clock_tree_delay() Diogo Ivo
2024-04-24 18:16 ` [PATCH v2 0/7] Cleanup Tegra210 EMC frequency scaling Krzysztof Kozlowski
2024-04-25 6:11 ` Krzysztof Kozlowski
2024-04-27 17:05 ` Diogo Ivo
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=20240419104516.308975-1-diogo.ivo@tecnico.ulisboa.pt \
--to=diogo.ivo@tecnico.ulisboa.pt \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@linaro.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).