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: <20190906232346.8435-1-jorge.ramirez-ortiz@linaro.org>
References: <20190906232346.8435-1-jorge.ramirez-ortiz@linaro.org>
Cc:     bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
        linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
To:     agross@kernel.org, jorge.ramirez-ortiz@linaro.org,
        mturquette@baylibre.com
From:   Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] clk: qcom: fix QCS404 TuringCC regmap
User-Agent: alot/0.8.1
Date:   Mon, 09 Sep 2019 01:19:36 -0700
Message-Id: <20190909081937.13E0920678@mail.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting Jorge Ramirez-Ortiz (2019-09-06 16:23:46)
> The max register is 0x23004 as per the manual (the current
> max_register that this commit is fixing is actually out of bounds).
>=20
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
> ---

Fixes tag?

>  drivers/clk/qcom/turingcc-qcs404.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>=20
> diff --git a/drivers/clk/qcom/turingcc-qcs404.c b/drivers/clk/qcom/turing=
cc-qcs404.c
> index aa859e6ec9bd..4cfbbf5bf4d9 100644
> --- a/drivers/clk/qcom/turingcc-qcs404.c
> +++ b/drivers/clk/qcom/turingcc-qcs404.c
> @@ -96,7 +96,7 @@ static const struct regmap_config turingcc_regmap_confi=
g =3D {
>         .reg_bits       =3D 32,
>         .reg_stride     =3D 4,
>         .val_bits       =3D 32,
> -       .max_register   =3D 0x30000,
> +       .max_register   =3D 0x23004,
>         .fast_io        =3D true,
>  };
> =20
> --=20
> 2.23.0
>=20