From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: cassel@kernel.org, linux-ide@vger.kernel.org, dlemoal@kernel.org
Subject: Re: [PATCH 1/5] ata: sata_dwc_460ex: use device_property_present()
Date: Tue, 30 Jun 2026 20:36:02 +0000 [thread overview]
Message-ID: <20260630203603.0FAA51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260630202415.234463-2-rosenp@gmail.com>
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
New issues:
- [Low] Incomplete refactoring: missed identical `of_property_present` pattern.
- [Low] Direct usage of `device_property_present()` without including `<linux/property.h>`.
Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but `clear_interrupt_bit()` ignores its `bit` argument and accidentally clears all pending interrupts.
--
commit 3c350702aea5f359b0516233c160076946c26124
Author: Rosen Penev <rosenp@gmail.com>
ata: sata_dwc_460ex: use device_property_present()
There's no need to use np here when dev is enough. Follows the similar
pattern elsewhere where of APIs are replaced with device ones,
especially when using platform_device.
> diff --git a/drivers/ata/sata_dwc_460ex.c b/drivers/ata/sata_dwc_460ex.c
> index 4fc22ce4bd9aa..2bcb3ac5ae211 100644
> --- a/drivers/ata/sata_dwc_460ex.c
> +++ b/drivers/ata/sata_dwc_460ex.c
> @@ -1180,7 +1180,7 @@ static int sata_dwc_probe(struct platform_device *ofdev)
> }
>
> #ifdef CONFIG_SATA_DWC_OLD_DMA
> - if (!of_property_present(np, "dmas")) {
> + if (!device_property_present(dev, "dmas")) {
[Severity: Low]
Does this require including linux/property.h? The build currently succeeds
due to transitive includes, but it might be safer to include the header
directly to prevent future build breakages if the include chain changes.
[Severity: Low]
Is the intention to replace all of_property_present usages? Looking at
sata_dwc_dma_get_channel() in the same file, it still uses the old function:
if (!of_property_present(dev->of_node, "dmas"))
Should this be updated as well for consistency?
[Severity: High]
This is a pre-existing issue, but clear_interrupt_bit() seems to ignore its
bit argument and accidentally clears all pending interrupts:
static void clear_interrupt_bit(struct sata_dwc_device *hsdev, u32 bit)
{
sata_dwc_writel(&hsdev->sata_dwc_regs->intpr,
sata_dwc_readl(&hsdev->sata_dwc_regs->intpr));
}
Because it reads the entire intpr register and writes it back unmodified,
does this acknowledge and clear all pending interrupts in the write-1-to-clear
register instead of just the requested bit? This could drop device
interrupts when multiple interrupts are asserted simultaneously.
> err = sata_dwc_dma_init_old(ofdev, hsdev);
> if (err)
> return err;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260630202415.234463-1-rosenp@gmail.com?part=1
next prev parent reply other threads:[~2026-06-30 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 20:24 [PATCH 0/5] ata: sata_dwc_460ex: cleanups and interrupt ordering fix Rosen Penev
2026-06-30 20:24 ` [PATCH 1/5] ata: sata_dwc_460ex: use device_property_present() Rosen Penev
2026-06-30 20:36 ` sashiko-bot [this message]
2026-06-30 20:24 ` [PATCH 2/5] ata: sata_dwc_460ex: use platform_get_irq() Rosen Penev
2026-06-30 20:24 ` [PATCH 3/5] ata: sata_dwc_460ex: use devm for old DMA resource lifetime management Rosen Penev
2026-06-30 20:24 ` [PATCH 4/5] ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered Rosen Penev
2026-06-30 20:36 ` sashiko-bot
2026-06-30 20:24 ` [PATCH 5/5] ata: sata_dwc_460ex: drop redundant struct copy of port_info Rosen Penev
-- strict thread matches above, loose matches on Subject: below --
2026-06-30 20:24 [PATCH 0/5] ata: sata_dwc_460ex: cleanups and interrupt ordering fix Rosen Penev
2026-06-30 20:24 ` [PATCH 1/5] ata: sata_dwc_460ex: use device_property_present() Rosen Penev
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=20260630203603.0FAA51F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=rosenp@gmail.com \
--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