From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-samsung-soc@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-pm@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Alim Akhtar <alim.akhtar@samsung.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-tegra@vger.kernel.org,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-stm32@st-md-mailman.stormreply.com,
Lukasz Luba <lukasz.luba@arm.com>
Subject: Re: [PATCH 3/9] memory: samsung: exynos5422-dmc: use scoped device node handling to simplify error paths
Date: Wed, 14 Aug 2024 17:42:46 +0100 [thread overview]
Message-ID: <20240814174246.00007e4e@Huawei.com> (raw)
In-Reply-To: <20240812-cleanup-h-of-node-put-memory-v1-3-5065a8f361d2@linaro.org>
On Mon, 12 Aug 2024 15:33:57 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> Obtain the device node reference with scoped/cleanup.h to reduce error
> handling and make the code a bit simpler.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Trivial comments inline
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> drivers/memory/samsung/exynos5422-dmc.c | 31 +++++++++++--------------------
> 1 file changed, 11 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/memory/samsung/exynos5422-dmc.c b/drivers/memory/samsung/exynos5422-dmc.c
> index da7ecd921c72..d3ae4d95a3ba 100644
> --- a/drivers/memory/samsung/exynos5422-dmc.c
> +++ b/drivers/memory/samsung/exynos5422-dmc.c
> @@ -4,6 +4,7 @@
> * Author: Lukasz Luba <l.luba@partner.samsung.com>
> */
>
> +#include <linux/cleanup.h>
> #include <linux/clk.h>
> #include <linux/devfreq.h>
> #include <linux/devfreq-event.h>
> @@ -1176,10 +1177,10 @@ static int of_get_dram_timings(struct exynos5_dmc *dmc)
> {
> int ret = 0;
> int idx;
> - struct device_node *np_ddr;
This would definitely benefit from a
struct device *dev = dmc->dev;
> u32 freq_mhz, clk_period_ps;
>
> - np_ddr = of_parse_phandle(dmc->dev->of_node, "device-handle", 0);
> + struct device_node *np_ddr __free(device_node) = of_parse_phandle(dmc->dev->of_node,
> + "device-handle", 0);
Trivial. Maybe consider the wrap suggested in patch 1.
> + struct device_node *np_ddr __free(device_node) =
of_parse_phandle(dmc->dev->of_node, "device-handle", 0);
> if (!np_ddr) {
> dev_warn(dmc->dev, "could not find 'device-handle' in DT\n");
> return -EINVAL;
> @@ -1187,39 +1188,31 @@ static int of_get_dram_timings(struct exynos5_dmc *dmc)
>
> dmc->timing_row = devm_kmalloc_array(dmc->dev, TIMING_COUNT,
> sizeof(u32), GFP_KERNEL);
> - if (!dmc->timing_row) {
> - ret = -ENOMEM;
> - goto put_node;
> - }
> + if (!dmc->timing_row)
> + return -ENOMEM;
>
> dmc->timing_data = devm_kmalloc_array(dmc->dev, TIMING_COUNT,
> sizeof(u32), GFP_KERNEL);
> - if (!dmc->timing_data) {
> - ret = -ENOMEM;
> - goto put_node;
> - }
> + if (!dmc->timing_data)
> + return -ENOMEM;
>
> dmc->timing_power = devm_kmalloc_array(dmc->dev, TIMING_COUNT,
> sizeof(u32), GFP_KERNEL);
> - if (!dmc->timing_power) {
> - ret = -ENOMEM;
> - goto put_node;
> - }
> + if (!dmc->timing_power)
> + return -ENOMEM;
>
> dmc->timings = of_lpddr3_get_ddr_timings(np_ddr, dmc->dev,
> DDR_TYPE_LPDDR3,
> &dmc->timings_arr_size);
> if (!dmc->timings) {
> dev_warn(dmc->dev, "could not get timings from DT\n");
> - ret = -EINVAL;
> - goto put_node;
> + return -EINVAL;
> }
>
> dmc->min_tck = of_lpddr3_get_min_tck(np_ddr, dmc->dev);
> if (!dmc->min_tck) {
> dev_warn(dmc->dev, "could not get tck from DT\n");
> - ret = -EINVAL;
> - goto put_node;
> + return -EINVAL;
> }
>
> /* Sorted array of OPPs with frequency ascending */
> @@ -1239,8 +1232,6 @@ static int of_get_dram_timings(struct exynos5_dmc *dmc)
> dmc->bypass_timing_data = dmc->timing_data[idx - 1];
> dmc->bypass_timing_power = dmc->timing_power[idx - 1];
>
> -put_node:
> - of_node_put(np_ddr);
> return ret;
> }
>
>
next prev parent reply other threads:[~2024-08-14 16:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 13:33 [PATCH 0/9] memory: simplify with scoped/cleanup.h for device nodes Krzysztof Kozlowski
2024-08-12 13:33 ` [PATCH 1/9] memory: atmel-ebi: use scoped device node handling to simplify error paths Krzysztof Kozlowski
2024-08-14 16:38 ` Jonathan Cameron
2024-08-14 17:56 ` Krzysztof Kozlowski
2024-08-12 13:33 ` [PATCH 2/9] memory: atmel-ebi: simplify with scoped for each OF child loop Krzysztof Kozlowski
2024-08-14 16:39 ` Jonathan Cameron
2024-08-12 13:33 ` [PATCH 3/9] memory: samsung: exynos5422-dmc: use scoped device node handling to simplify error paths Krzysztof Kozlowski
2024-08-14 16:42 ` Jonathan Cameron [this message]
2024-08-14 17:57 ` Krzysztof Kozlowski
2024-08-12 13:33 ` [PATCH 4/9] memory: stm32-fmc2-ebi: simplify with scoped for each OF child loop Krzysztof Kozlowski
2024-08-14 16:45 ` Jonathan Cameron
2024-08-14 17:59 ` Krzysztof Kozlowski
2024-08-12 13:33 ` [PATCH 5/9] memory: tegra-mc: " Krzysztof Kozlowski
2024-08-14 16:50 ` Jonathan Cameron
2024-08-12 13:34 ` [PATCH 6/9] memory: tegra124-emc: " Krzysztof Kozlowski
2024-08-14 16:51 ` Jonathan Cameron
2024-08-12 13:34 ` [PATCH 7/9] memory: tegra20-emc: " Krzysztof Kozlowski
2024-08-14 16:52 ` Jonathan Cameron
2024-08-12 13:34 ` [PATCH 8/9] memory: tegra30-emc: " Krzysztof Kozlowski
2024-08-12 13:34 ` [PATCH 9/9] memory: ti-aemif: " Krzysztof Kozlowski
2024-08-14 16:55 ` Jonathan Cameron
2024-08-14 18:01 ` 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=20240814174246.00007e4e@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alim.akhtar@samsung.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-tegra@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ssantosh@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 NNTP newsgroup(s).