From: Krzysztof Kozlowski <krzk@kernel.org>
To: Petar Stepanovic <pstepanovic@axiado.com>
Cc: "Akhila Kavi" <akavi@axiado.com>,
"Prasad Bolisetty" <pbolisetty@axiado.com>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Harshit Shah" <hshah@axiado.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] pwm: add Axiado AX3000 PWM driver
Date: Fri, 24 Jul 2026 10:36:25 +0200 [thread overview]
Message-ID: <20260724-comical-chubby-dragon-9c73ff@quoll> (raw)
In-Reply-To: <20260723-axiado-ax3000-pwm-v2-2-22002f0b281d@axiado.com>
On Thu, Jul 23, 2026 at 02:32:19AM -0700, Petar Stepanovic wrote:
> + chip->ops = &axiado_pwm_ops;
> + chip->atomic = true;
> +
> + ret = devm_pwmchip_add(dev, chip);
> + if (ret)
> + return dev_err_probe(dev, ret, "Failed to add PWM chip\n");
> +
> + return 0;
> +}
> +
> +static const struct of_device_id axiado_pwm_match[] = {
> + { .compatible = "axiado,ax3000-pwm" },
> + { .compatible = "axiado,ax3005-pwm" },
This suggests deviecs are fully compatible, so drop the second entry and
express compatibility (see writing bindings, example schema, DTS101
talk/slides).
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-24 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723-axiado-ax3000-pwm-v2-0-22002f0b281d@axiado.com>
[not found] ` <20260723-axiado-ax3000-pwm-v2-1-22002f0b281d@axiado.com>
2026-07-24 8:35 ` [PATCH v2 1/2] dt-bindings: pwm: add Axiado AX3000 PWM Krzysztof Kozlowski
[not found] ` <20260723-axiado-ax3000-pwm-v2-2-22002f0b281d@axiado.com>
2026-07-24 8:36 ` 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=20260724-comical-chubby-dragon-9c73ff@quoll \
--to=krzk@kernel.org \
--cc=akavi@axiado.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hshah@axiado.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pbolisetty@axiado.com \
--cc=pstepanovic@axiado.com \
--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