From: "Kumar, Udit" <u-kumar1@ti.com>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>, <lgirdwood@gmail.com>,
<linux-kernel@vger.kernel.org>
Cc: <m-leonard@ti.com>, <n-francis@ti.com>, <bhargav.r@ltts.com>,
<m.nirmaladevi@ltts.com>, <vigneshr@ti.com>
Subject: Re: [PATCH v1 1/1] Correct nr_types assignment for TPS6594/3 and TPS65224
Date: Mon, 3 Jun 2024 22:46:18 +0530 [thread overview]
Message-ID: <63167c3f-f583-4b2d-83c8-632827594ebb@ti.com> (raw)
In-Reply-To: <20240603170524.643010-2-s-ramamoorthy@ti.com>
On 6/3/2024 10:35 PM, Shree Ramamoorthy wrote:
> Swap nr_types assignment for TPS6594/3 and TPS65224.
> Issue detected with v6.10-rc1 and tested using a TI J7200 EVM board.
Please prefix line, where you want this patch to go
like tiL6.6 or so
> Log:
> [ 13.974024] Call trace:
> [ 13.974025] _regulator_put.part.0+0x40/0x48
> [ 13.974028] regulator_register+0x2b0/0xa00
> [ 13.974031] devm_regulator_register+0x58/0xa0
> [ 13.974035] tps6594_regulator_probe+0x4e0/0x5f0 [tps6594_regulator]
> ...
> [ 13.974178] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004
>
> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
> ---
> drivers/regulator/tps6594-regulator.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/regulator/tps6594-regulator.c b/drivers/regulator/tps6594-regulator.c
> index 4a859f4c0f83..b66608ab2546 100644
> --- a/drivers/regulator/tps6594-regulator.c
> +++ b/drivers/regulator/tps6594-regulator.c
> @@ -660,11 +660,11 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> } else if (tps->chip_id == TPS65224) {
> nr_buck = ARRAY_SIZE(tps65224_buck_regs);
> nr_ldo = ARRAY_SIZE(tps65224_ldo_regs);
> - nr_types = REGS_INT_NB;
> + nr_types = TPS65224_REGS_INT_NB;
> } else {
> nr_buck = ARRAY_SIZE(buck_regs);
> nr_ldo = ARRAY_SIZE(tps6594_ldo_regs);
> - nr_types = TPS65224_REGS_INT_NB;
> + nr_types = REGS_INT_NB;
> }
>
> reg_irq_nb = nr_types * (nr_buck + nr_ldo);
> --
next prev parent reply other threads:[~2024-06-03 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:05 [PATCH v1 0/1] regulator: tps6594-regulator: Correct nr_types assignment Shree Ramamoorthy
2024-06-03 17:05 ` [PATCH v1 1/1] Correct nr_types assignment for TPS6594/3 and TPS65224 Shree Ramamoorthy
2024-06-03 17:16 ` Kumar, Udit [this message]
2024-06-03 17:29 ` Kumar, Udit
2024-06-03 17:31 ` Vignesh Raghavendra
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=63167c3f-f583-4b2d-83c8-632827594ebb@ti.com \
--to=u-kumar1@ti.com \
--cc=bhargav.r@ltts.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=m.nirmaladevi@ltts.com \
--cc=n-francis@ti.com \
--cc=s-ramamoorthy@ti.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®