Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1573120694-6015-1-git-send-email-rajan.vaja@xilinx.com>
References: <1573120694-6015-1-git-send-email-rajan.vaja@xilinx.com>
From:   Stephen Boyd <sboyd@kernel.org>
To:     Rajan Vaja <rajan.vaja@xilinx.com>, jolly.shah@xilinx.com,
        michal.simek@xilinx.com, mturquette@baylibre.com,
        nava.manne@xilinx.com, shubhrajyoti.datta@xilinx.com,
        tejas.patel@xilinx.com
Cc:     linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org, Rajan Vaja <rajan.vaja@xilinx.com>
Subject: Re: [PATCH] clk: zynqmp: Warn user if clock user are more than allowed
User-Agent: alot/0.8.1
Date:   Thu, 07 Nov 2019 11:23:17 -0800
Message-Id: <20191107192318.3E31B2084C@mail.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting Rajan Vaja (2019-11-07 01:58:14)
> Warn user if clock is used by more than allowed devices.
> This check is done by firmware and returns respective
> error code. Upon receiving error code for excessive user,
> warn user for the same.
>=20
> This change is done to restrict VPLL use count. It is
> assumed that VPLL is used by one user only.
>=20
> Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>

This sign off chain is incorrect.

> ---
>  drivers/clk/zynqmp/pll.c             | 9 ++++++---
>  drivers/firmware/xilinx/zynqmp.c     | 2 ++
>  include/linux/firmware/xlnx-zynqmp.h | 1 +
>  3 files changed, 9 insertions(+), 3 deletions(-)
>=20
> diff --git a/drivers/clk/zynqmp/pll.c b/drivers/clk/zynqmp/pll.c
> index a541397..2f4ccaa 100644
> --- a/drivers/clk/zynqmp/pll.c
> +++ b/drivers/clk/zynqmp/pll.c
> @@ -188,9 +188,12 @@ static int zynqmp_pll_set_rate(struct clk_hw *hw, un=
signed long rate,
>                 frac =3D (parent_rate * f) / FRAC_DIV;
> =20
>                 ret =3D eemi_ops->clock_setdivider(clk_id, m);
> -               if (ret)
> -                       pr_warn_once("%s() set divider failed for %s, ret=
 =3D %d\n",
> -                                    __func__, clk_name, ret);
> +               if (ret) {
> +                       if (ret =3D=3D -EUSERS)
> +                               WARN(1, "More than allowed devices are us=
ing the %s, which is forbidden\n", clk_name);
> +                       pr_err("%s() set divider failed for %s, ret =3D %=
d\n",
> +                              __func__, clk_name, ret);
> +               }

Shouldn't we catch this much earlier when clk_get() is called or
something like that?

> =20
>                 eemi_ops->ioctl(0, IOCTL_SET_PLL_FRAC_DATA, clk_id, f, NU=
LL);
> =20
> diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/z=
ynqmp.c
> index 75bdfaa..74d9f13 100644
> --- a/drivers/firmware/xilinx/zynqmp.c
> +++ b/drivers/firmware/xilinx/zynqmp.c
> @@ -48,6 +48,8 @@ static int zynqmp_pm_ret_code(u32 ret_status)
>                 return -EACCES;
>         case XST_PM_ABORT_SUSPEND:
>                 return -ECANCELED;
> +       case XST_PM_MULT_USER:
> +               return -EUSERS;

This is for filesystem quotas? It's a weird error return value.

>         case XST_PM_INTERNAL:
>         case XST_PM_CONFLICT:
>         case XST_PM_INVALID_NODE: