From: sashiko-bot@kernel.org
To: "Ali Rouhi" <arouhi@sitime.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v13 04/12] dpll: sit9531x: read DPLL types and pin properties from system firmware
Date: Wed, 14 Oct 2026 22:41:46 +0000 [thread overview]
Message-ID: <sashiko-outbox-171991@kernel.org> (raw)
In-Reply-To: <20261013224131.27149-5-arouhi@sitime.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dpll: state leak on error path for XO pin
--
commit 1b38c14d1669809a7ef952760c8da64d9afcc03c
Author: Oleg Zadorozhnyi <Oleg.Zadorozhnyi@devoxsoftware.com>
dpll: sit9531x: read DPLL types and pin properties from system firmware
The DPLL core wants a type per device and a property set per pin: a
label, the direction, the capabilities, and the frequencies the pin
supports. None of that can be read from the chip, so they come
from the firmware node.
> diff --git a/drivers/dpll/sit9531x/prop.c b/drivers/dpll/sit9531x/prop.c
> new file mode 100644
> index 0000000000000..3635ea497e415
> --- /dev/null
> +++ b/drivers/dpll/sit9531x/prop.c
[ ... ]
> +struct sit9531x_pin_props *
> +sit9531x_pin_props_get(struct sit9531x_dev *sitdev,
> + enum dpll_pin_direction dir, u8 index)
> +{
[ ... ]
> + } else if (dir == DPLL_PIN_DIRECTION_INPUT &&
> + index == SIT9531X_MAX_INPUTS) {
> + /* The XO reference is fixed: no state or priority control. */
> + props->dpll_props.type = DPLL_PIN_TYPE_INT_OSCILLATOR;
> + props->dpll_props.capabilities = 0;
> + sitdev->ref[index].freq = sitdev->xtal_freq;
[Severity: Low]
Does this code leak state if an allocation fails later in the function?
The comment later in sit9531x_pin_props_get() explicitly states that the
allocation for ranges is the last thing that can fail, and a call that reports
failure must not leave the device's cached rate changed behind it.
However, if the allocation for ranges fails, the function returns -ENOMEM
and leaves sitdev->ref[index].freq permanently modified for the XO pin.
Should the update to sitdev->ref[index].freq be deferred to the end of the
function here as well, rather than doing it early in this block?
> + curr_freq = sitdev->xtal_freq;
> + } else if (dir == DPLL_PIN_DIRECTION_INPUT) {
[ ... ]
> + ranges = kcalloc(num_freqs + 2, sizeof(*ranges), GFP_KERNEL);
> + if (!ranges) {
> + rc = -ENOMEM;
> + goto err_alloc_ranges;
> + }
> +
> + /*
> + * Publish the seeded rate only once the pin is certain to be built.
> + * The allocation above is the last thing that can fail, and a call
> + * that reports failure must not leave the device's cached rate
> + * changed behind it.
> + */
> + if (curr_freq) {
> + if (dir == DPLL_PIN_DIRECTION_INPUT)
> + sitdev->ref[index].freq = curr_freq;
> + else
> + sitdev->out[index].freq = curr_freq;
> + }
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013224131.27149-1-arouhi@sitime.com?part=4
next prev parent reply other threads:[~2026-10-14 22:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 22:41 [PATCH net-next v13 00/12] dpll: add SiTime SiT9531x DPLL clock driver Ali Rouhi
2026-10-13 22:41 ` [PATCH net-next v13 01/12] dt-bindings: vendor-prefixes: add SiTime Corporation Ali Rouhi
2026-10-13 22:41 ` [PATCH net-next v13 02/12] dt-bindings: dpll: add SiTime SiT95316 clock generator Ali Rouhi
2026-10-14 22:41 ` sashiko-bot
2026-10-13 22:41 ` [PATCH net-next v13 03/12] dpll: add basic SiTime SiT9531x support Ali Rouhi
2026-10-13 22:41 ` [PATCH net-next v13 04/12] dpll: sit9531x: read DPLL types and pin properties from system firmware Ali Rouhi
2026-10-14 22:41 ` sashiko-bot [this message]
2026-10-13 22:41 ` [PATCH net-next v13 05/12] dpll: sit9531x: register DPLL devices and pins Ali Rouhi
2026-10-14 22:41 ` sashiko-bot
2026-10-13 22:41 ` [PATCH net-next v13 06/12] dpll: sit9531x: implement input pin state on a DPLL Ali Rouhi
2026-10-13 22:41 ` [PATCH net-next v13 08/12] dpll: sit9531x: add support to get and set frequency on pins Ali Rouhi
2026-10-14 22:41 ` sashiko-bot
2026-10-13 22:41 ` [PATCH net-next v13 07/12] dpll: sit9531x: add support to get and set priority on input pins Ali Rouhi
2026-10-13 22:41 ` [PATCH net-next v13 10/12] dpll: sit9531x: add support to adjust output phase Ali Rouhi
2026-10-14 22:41 ` sashiko-bot
2026-10-13 22:41 ` [PATCH net-next v13 09/12] dpll: sit9531x: implement output pin state on a DPLL Ali Rouhi
2026-10-13 22:41 ` [PATCH net-next v13 12/12] dpll: sit9531x: model the inter-PLL sync net as a pair of pins Ali Rouhi
2026-10-14 22:41 ` sashiko-bot
2026-10-13 22:41 ` [PATCH net-next v13 11/12] dpll: sit9531x: add support to get phase offset on the connected input pin Ali Rouhi
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=sashiko-outbox-171991@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=arouhi@sitime.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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