From: Stephen Boyd <sboyd@kernel.org>
To: Rohit Visavalia <rohit.visavalia@amd.com>,
michal.simek@amd.com, mturquette@baylibre.com,
vishal.sagar@amd.com
Cc: javier.carrasco.cruz@gmail.com, geert+renesas@glider.be,
u.kleine-koenig@baylibre.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Rohit Visavalia <rohit.visavalia@amd.com>
Subject: Re: [PATCH 1/3] clk: xilinx: vcu: Update vcu init/reset sequence
Date: Mon, 30 Dec 2024 16:39:23 -0800 [thread overview]
Message-ID: <5227cdd506bcb0239657216bd36de12f.sboyd@kernel.org> (raw)
In-Reply-To: <20241226122023.3439559-2-rohit.visavalia@amd.com>
Quoting Rohit Visavalia (2024-12-26 04:20:21)
> diff --git a/drivers/clk/xilinx/xlnx_vcu.c b/drivers/clk/xilinx/xlnx_vcu.c
> index 81501b48412e..f294a2398cb4 100644
> --- a/drivers/clk/xilinx/xlnx_vcu.c
> +++ b/drivers/clk/xilinx/xlnx_vcu.c
> @@ -676,6 +679,24 @@ static int xvcu_probe(struct platform_device *pdev)
> * Bit 0 : Gasket isolation
> * Bit 1 : put VCU out of reset
> */
> + xvcu->reset_gpio = devm_gpiod_get_optional(&pdev->dev, "reset",
> + GPIOD_OUT_LOW);
> + if (IS_ERR(xvcu->reset_gpio)) {
> + ret = PTR_ERR(xvcu->reset_gpio);
> + dev_err(&pdev->dev, "failed to get reset gpio for vcu.\n");
Use dev_err_probe() and friends.
> + goto error_get_gpio;
> + }
> +
> + if (xvcu->reset_gpio) {
> + gpiod_set_value(xvcu->reset_gpio, 0);
> + /* min 2 clock cycle of vcu pll_ref, slowest freq is 33.33KHz */
> + usleep_range(60, 120);
> + gpiod_set_value(xvcu->reset_gpio, 1);
> + usleep_range(60, 120);
> + } else {
> + dev_warn(&pdev->dev, "No reset gpio info from dts for vcu. This may lead to incorrect functionality if VCU isolation is removed post initialization.\n");
Is it 'vcu' or 'VCU'? Pick one please. Also, this is going to be an
unfixable warning message if the reset isn't there. Why have this
warning at all?
next prev parent reply other threads:[~2024-12-31 0:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 12:20 [PATCH 0/3] clk: xilinx: vcu: Sequence update and couple of fixes Rohit Visavalia
2024-12-26 12:20 ` [PATCH 1/3] clk: xilinx: vcu: Update vcu init/reset sequence Rohit Visavalia
2024-12-31 0:39 ` Stephen Boyd [this message]
2024-12-31 14:16 ` Visavalia, Rohit
2024-12-31 14:26 ` Geert Uytterhoeven
2025-01-02 7:01 ` Visavalia, Rohit
2025-01-02 9:58 ` Geert Uytterhoeven
2025-01-02 10:05 ` Visavalia, Rohit
2024-12-26 12:20 ` [PATCH 2/3] clk: xilinx: vcu: don't set pll_ref as parent of VCU(enc/dec) clocks Rohit Visavalia
2024-12-31 0:35 ` Stephen Boyd
2024-12-31 14:16 ` Visavalia, Rohit
2024-12-26 12:20 ` [PATCH 3/3] clk: xilinx: vcu: unregister pll_post only if registered correctly Rohit Visavalia
2024-12-31 0:37 ` Stephen Boyd
2024-12-31 14:16 ` Visavalia, Rohit
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=5227cdd506bcb0239657216bd36de12f.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=geert+renesas@glider.be \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=rohit.visavalia@amd.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vishal.sagar@amd.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.