From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ben Zong-You Xie <ben717@andestech.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: ukleinek@kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [v3 2/2] pwm: atcpit100: add Andes PWM driver support
Date: Sun, 9 Feb 2025 12:16:58 +0100 [thread overview]
Message-ID: <642f00de-d133-4c59-8dd3-f2ba0107b322@kernel.org> (raw)
In-Reply-To: <Z6RuGrszOiPFWHyU@atctrx.andestech.com>
On 06/02/2025 09:08, Ben Zong-You Xie wrote:
> On Fri, Jan 24, 2025 at 08:30:48AM +0100, Krzysztof Kozlowski wrote:
>> [EXTERNAL MAIL]
>>
>> On 23/01/2025 20:35, Ben Zong-You Xie wrote:
>>>
>>> +config PWM_ATCPIT100
>>> + tristate "Andes ATCPIT100 PWM support"
>>> + depends on OF && HAS_IOMEM
>>> + depends on RISCV || COMPILE_TEST
>>> + select REGMAP_MMIO
>>> + help
>>> + Generic PWM framework driver for ATCPIT100 on Andes AE350 platform
>>
>>
>> Is AE350 a type of a SoC? Looks like. "depends on RISCV" is wrong -
>> there is nothing RISC-V specific here. You must depend on given
>> SoC/platform.
>>
>
> Hi Krzysztof,
>
> AE350 is not a SoC. It's just a reference platform to verify Andes CPUs
> on FPGA. For further information on AE350, please refer to [1].
Then what is the SoC?
>
> Also, I will remove "depends on RISCV" and fix the coding style problems
No, read the review again and implement it:
"You must depend on given SoC/platform."
Best regards,
Krzysztof
prev parent reply other threads:[~2025-02-09 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 19:35 [v3 0/2] pwm: add PWM driver for atcpit100 Ben Zong-You Xie
2025-01-23 19:35 ` [v3 1/2] dt-bindings: pwm: add atcpit100 Ben Zong-You Xie
2025-01-24 7:27 ` Krzysztof Kozlowski
2025-01-23 19:35 ` [v3 2/2] pwm: atcpit100: add Andes PWM driver support Ben Zong-You Xie
2025-01-24 7:30 ` Krzysztof Kozlowski
2025-02-06 8:08 ` Ben Zong-You Xie
2025-02-06 11:45 ` Uwe Kleine-König
2025-02-09 11:16 ` Krzysztof Kozlowski [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=642f00de-d133-4c59-8dd3-f2ba0107b322@kernel.org \
--to=krzk@kernel.org \
--cc=ben717@andestech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ukleinek@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