From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kevin Chen <kevin_chen@aspeedtech.com>,
lee@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, joel@jms.id.au, andrew@codeconstruct.com.au,
derek.kiernan@amd.com, dragan.cvetic@amd.com, arnd@arndb.de,
gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] soc: aspeed: lpc-pcc: Add PCC controller support
Date: Tue, 11 Mar 2025 08:34:47 +0100 [thread overview]
Message-ID: <0e30c12f-5ac5-4008-8cc8-ec4111520655@kernel.org> (raw)
In-Reply-To: <20250310114839.3098148-4-kevin_chen@aspeedtech.com>
On 10/03/2025 12:48, Kevin Chen wrote:
> +static int aspeed_pcc_probe(struct platform_device *pdev)
> +{
> + int rc;
> + struct aspeed_pcc_ctrl *pcc;
> + struct device *dev = &pdev->dev;
> + uint32_t fifo_size = PAGE_SIZE;
> +
> + pcc = devm_kzalloc(dev, sizeof(*pcc), GFP_KERNEL);
> + if (!pcc)
> + return -ENOMEM;
> +
> + pcc->regmap = syscon_node_to_regmap(dev->parent->of_node);
> + if (IS_ERR(pcc->regmap)) {
> + dev_err(dev, "Couldn't get regmap\n");
return dev_err_probe() is not suitable?
> + return -ENODEV;
Why overriding error code?
> + }
> +
> + rc = of_property_read_u32(dev->of_node, "pcc-ports", &pcc->port);
> + if (rc) {
> + dev_err(dev, "no pcc ports configured\n");
> + return -ENODEV;
Why overriding error code?
You got this comment already at v2.
> + }
> +
> + rc = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64));
> + if (rc) {
> + dev_err(dev, "cannot set 64-bits DMA mask\n");
> + return rc;
> + }
> +
> + pcc->dma.size = PCC_DMA_BUFSZ;
> + pcc->dma.virt = dmam_alloc_coherent(dev,
> + pcc->dma.size,
> + &pcc->dma.addr,
> + GFP_KERNEL);
> + if (!pcc->dma.virt) {
> + dev_err(dev, "cannot allocate DMA buffer\n");
> + return -ENOMEM;
> + }
> +
> + fifo_size = roundup(pcc->dma.size, PAGE_SIZE);
> + rc = kfifo_alloc(&pcc->fifo, fifo_size, GFP_KERNEL);
> + if (rc) {
Drop {}
> + return -ENOMEM;
> + }
> +
Please run scripts/checkpatch.pl and fix reported warnings. After that,
run also `scripts/checkpatch.pl --strict` and (probably) fix more
warnings. Some warnings can be ignored, especially from --strict run,
but the code here looks like it needs a fix. Feel free to get in touch
if the warning is not clear.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-11 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:48 [PATCH v3 0/3] Add AST2600 LPC PCC support Kevin Chen
2025-03-10 11:48 ` [PATCH v3 1/3] dt-binding: aspeed: Add LPC PCC controller Kevin Chen
2025-03-11 7:32 ` Krzysztof Kozlowski
2025-03-10 11:48 ` [PATCH v3 2/3] ARM: dts: aspeed-g6: Add AST2600 LPC PCC support Kevin Chen
2025-03-10 11:48 ` [PATCH v3 3/3] soc: aspeed: lpc-pcc: Add PCC controller support Kevin Chen
2025-03-11 7:34 ` Krzysztof Kozlowski [this message]
2025-03-14 10:56 ` Kevin Chen
2025-03-15 19:41 ` kernel test robot
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=0e30c12f-5ac5-4008-8cc8-ec4111520655@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=derek.kiernan@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=kevin_chen@aspeedtech.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).