From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-usb@vger.kernel.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"open list:QUALCOMM TYPEC PORT MANAGER DRIVER"
<linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL HARDENING (not covered by other
areas):Keyword:b__counted_by(_le|_be)?b"
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH] usb: typec: qcom-pmic-typec: simplify allocation
Date: Thu, 12 Mar 2026 06:04:28 +0100 [thread overview]
Message-ID: <2026031252-slather-upscale-636e@gregkh> (raw)
In-Reply-To: <CAKxU2N_dJY60Tp4UgLMZ97ZJywNEktmA1At3z6VOPhhSCRx-1w@mail.gmail.com>
On Wed, Mar 11, 2026 at 11:54:55AM -0700, Rosen Penev wrote:
> On Wed, Mar 11, 2026 at 7:47 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, Mar 06, 2026 at 02:21:48PM -0800, Rosen Penev wrote:
> > > Change kzalloc + kcalloc to just kzalloc with a flexible array member.
> > >
> > > Add __counted_by for extra runtime analysis when requested.
> > >
> > > Shuffle some code in probe to provide a clearer picture.
> > >
> > > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > > ---
> > > .../typec/tcpm/qcom/qcom_pmic_typec_pdphy.c | 27 ++++++++-----------
> > > .../typec/tcpm/qcom/qcom_pmic_typec_port.c | 26 ++++++++----------
> > > 2 files changed, 22 insertions(+), 31 deletions(-)
> > >
> > > diff --git a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c
> > > index c8b1463e6e8b..4b3915c6894a 100644
> > > --- a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c
> > > +++ b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c
> > > @@ -95,13 +95,13 @@ struct pmic_typec_pdphy {
> > > struct regmap *regmap;
> > > u32 base;
> > >
> > > - unsigned int nr_irqs;
> > > - struct pmic_typec_pdphy_irq_data *irq_data;
> > > -
> > > struct work_struct reset_work;
> > > struct work_struct receive_work;
> > > struct regulator *vdd_pdphy;
> > > spinlock_t lock; /* Register atomicity */
> > > +
> > > + unsigned int nr_irqs;
> > > + struct pmic_typec_pdphy_irq_data irq_data[] __counted_by(nr_irqs);
> > > };
> > >
> > > static void qcom_pmic_typec_pdphy_reset_on(struct pmic_typec_pdphy *pmic_typec_pdphy)
> > > @@ -560,31 +560,26 @@ int qcom_pmic_typec_pdphy_probe(struct platform_device *pdev,
> > > struct pmic_typec_pdphy_irq_data *irq_data;
> > > int i, ret, irq;
> > >
> > > - pmic_typec_pdphy = devm_kzalloc(dev, sizeof(*pmic_typec_pdphy), GFP_KERNEL);
> > > - if (!pmic_typec_pdphy)
> > > - return -ENOMEM;
> > > -
> > > if (!res->nr_irqs || res->nr_irqs > PMIC_PDPHY_MAX_IRQS)
> > > return -EINVAL;
> > >
> > > - irq_data = devm_kcalloc(dev, res->nr_irqs, sizeof(*irq_data),
> > > - GFP_KERNEL);
> > > - if (!irq_data)
> > > + pmic_typec_pdphy = devm_kzalloc(dev, struct_size(pmic_typec_pdphy, irq_data, res->nr_irqs), GFP_KERNEL);
> >
> > extra long line, checkpatch.pl didn't complain about this?
> >
> > > + if (!pmic_typec_pdphy)
> > > return -ENOMEM;
> > >
> > > + pmic_typec_pdphy->nr_irqs = res->nr_irqs;
> > > + pmic_typec_pdphy->dev = dev;
> > > + pmic_typec_pdphy->base = base;
> > > + pmic_typec_pdphy->regmap = regmap;
> > > pmic_typec_pdphy->vdd_pdphy = devm_regulator_get(dev, "vdd-pdphy");
> > > if (IS_ERR(pmic_typec_pdphy->vdd_pdphy))
> > > return PTR_ERR(pmic_typec_pdphy->vdd_pdphy);
> > >
> > > - pmic_typec_pdphy->dev = dev;
> > > - pmic_typec_pdphy->base = base;
> > > - pmic_typec_pdphy->regmap = regmap;
> > > - pmic_typec_pdphy->nr_irqs = res->nr_irqs;
> > > - pmic_typec_pdphy->irq_data = irq_data;
> > > spin_lock_init(&pmic_typec_pdphy->lock);
> > > INIT_WORK(&pmic_typec_pdphy->reset_work, qcom_pmic_typec_pdphy_sig_reset_work);
> > >
> > > - for (i = 0; i < res->nr_irqs; i++, irq_data++) {
> > > + for (i = 0; i < res->nr_irqs; i++) {
> > > + irq_data = &pmic_typec_pdphy->irq_data[i];
> > > irq = platform_get_irq_byname(pdev, res->irq_params[i].irq_name);
> > > if (irq < 0)
> > > return irq;
> > > diff --git a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c
> > > index 8051eaa46991..7c5cf8061f04 100644
> > > --- a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c
> > > +++ b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c
> >
> > Can you just convert one driver at a time please? This should be a
> > patch series.
> This is not the same driver?
It's two different files, with two different structure allocations, so I
assumed it was two different ones. Either way, it should be two
different patches :)
thanks,
greg k-h
prev parent reply other threads:[~2026-03-12 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 22:21 [PATCH] usb: typec: qcom-pmic-typec: simplify allocation Rosen Penev
2026-03-07 7:21 ` Greg Kroah-Hartman
2026-03-07 7:54 ` Rosen Penev
2026-03-11 14:47 ` Greg Kroah-Hartman
2026-03-11 18:54 ` Rosen Penev
2026-03-12 5:04 ` Greg Kroah-Hartman [this message]
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=2026031252-slather-upscale-636e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bryan.odonoghue@linaro.org \
--cc=gustavoars@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kees@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rosenp@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