From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kevin Chen <kevin_chen@aspeedtech.com>,
"lee@kernel.org" <lee@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
"derek.kiernan@amd.com" <derek.kiernan@amd.com>,
"dragan.cvetic@amd.com" <dragan.cvetic@amd.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] soc: aspeed: lpc-pcc: Add PCC controller support
Date: Mon, 10 Mar 2025 12:43:29 +0100 [thread overview]
Message-ID: <58466532-3e17-4968-bade-210f478ccc76@kernel.org> (raw)
In-Reply-To: <TY0PR06MB496072786197162F19ED7DDD89D62@TY0PR06MB4960.apcprd06.prod.outlook.com>
On 10/03/2025 11:05, Kevin Chen wrote:
>> On 04/03/2025 11:44, Kevin Chen wrote:
>>> +
>>> +static int aspeed_pcc_probe(struct platform_device *pdev) {
>>> + int rc;
>>> + struct aspeed_pcc_ctrl *pcc;
>>> + struct device *dev;
>>> + uint32_t fifo_size = PAGE_SIZE;
>>> +
>>> + dev = &pdev->dev;
>>
>> This goes to declaration.
> OK. I will move it to declaration.
>
>>
>>> +
>>> + pcc = devm_kzalloc(&pdev->dev, sizeof(*pcc), GFP_KERNEL);
>>
>> Maybe my previous comment was not clear, but you agreed with it. Anyway
>> nothing improved here.
> Could I reserve the pcc variable using for the pcc_ctrl data structure?
> Pcc_ctrl data include the regmap/irq/io_port/dma/kfifo.
> If I change the name to dev, it does not make sense for these data to be.
>
>>
>> If you have 'dev' variable, use it.
> Do you mean just use the pdev->dev not local dev variable?
What is the point of this:
dev = &pdev->dev;
if you do not use 'dev'? If you come with a reason, sure. If you do not
have such, then everything should use 'dev', not pdev->dev.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-10 11:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:44 Add AST2600 LPC PCC support Kevin Chen
2025-03-04 10:44 ` [PATCH v2 1/3] dt-binding: aspeed: Add LPC PCC controller Kevin Chen
2025-03-05 6:38 ` Krzysztof Kozlowski
2025-03-10 1:50 ` Kevin Chen
2025-03-10 7:15 ` Krzysztof Kozlowski
2025-03-10 9:49 ` Kevin Chen
2025-03-10 11:42 ` Krzysztof Kozlowski
2025-03-11 0:22 ` Kevin Chen
2025-03-04 10:44 ` [PATCH v2 2/3] ARM: dts: aspeed-g6: Add AST2600 LPC PCC support Kevin Chen
2025-03-04 10:59 ` Krzysztof Kozlowski
2025-03-14 10:39 ` Kevin Chen
2025-03-04 10:44 ` [PATCH v2 3/3] soc: aspeed: lpc-pcc: Add PCC controller support Kevin Chen
2025-03-04 10:59 ` Krzysztof Kozlowski
2025-03-10 10:05 ` Kevin Chen
2025-03-10 11:43 ` Krzysztof Kozlowski [this message]
2025-03-11 0:17 ` Kevin Chen
2025-03-04 21:20 ` Christophe JAILLET
2025-03-10 2:15 ` Kevin Chen
2025-03-05 23:19 ` kernel test robot
2025-03-10 7:26 ` 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=58466532-3e17-4968-bade-210f478ccc76@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).