From: Billy Tsai <billy_tsai@aspeedtech.com> To: Krzysztof Kozlowski <krzk@kernel.org>, "jdelvare@suse.com" <jdelvare@suse.com>, "linux@roeck-us.net" <linux@roeck-us.net>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "joel@jms.id.au" <joel@jms.id.au>, "andrew@aj.id.au" <andrew@aj.id.au>, "lee.jones@linaro.org" <lee.jones@linaro.org>, "thierry.reding@gmail.com" <thierry.reding@gmail.com>, "u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>, "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>, "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.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>, "linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>, BMC-SW <BMC-SW@aspeedtech.com>, "garnermic@meta.com" <garnermic@meta.com> Subject: Re: [PATCH 1/3] dt-bindings: Add bindings for aspeed pwm-tach. Date: Thu, 3 Nov 2022 10:36:33 +0000 [thread overview] Message-ID: <2508B515-E153-42C2-B013-2A64A110BCF2@aspeedtech.com> (raw) In-Reply-To: <ee6c5a96-81c4-5729-f623-4b23bc3b8e0a@kernel.org> On 2022/11/3, 5:20 AM, "Krzysztof Kozlowski" <krzk@kernel.org> wrote: On 31/10/2022 06:38, Billy Tsai wrote: > > +patternProperties: > > + "^pwm(@[0-9a-f]+)?$": > > + $ref: ../pwm/aspeed,ast2600-pwm.yaml > Full path, so: /schemas/pwm/aspeed,ast2600-pwm.yaml > Why unit addresses are optional? > > + > > + "^tach(@[0-9a-f]+)?$": > > + $ref: ../hwmon/aspeed,ast2600-tach.yaml > Ditto > Why unit addresses are optional? The pwm_tach is not the bus. I will use pwm: type: object $ref: "/schemas/pwm/aspeed,ast2600-pwm.yaml" tach: type: object $ref: "/schemas/hwmon/aspeed,ast2600-tach.yaml" to replace it. > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/clock/ast2600-clock.h> > > + pwm_tach: pwm_tach@1e610000 { > Node names should be generic. > https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation This is the mfd with pwm and tach, so they are combined as the node name. > No underscores in node names. https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#table-1 I see that the underscore is the valid characters for node names. Did I miss any information? Thanks Best Regards, Billy Tsai
WARNING: multiple messages have this Message-ID (diff)
From: Billy Tsai <billy_tsai@aspeedtech.com> To: Krzysztof Kozlowski <krzk@kernel.org>, "jdelvare@suse.com" <jdelvare@suse.com>, "linux@roeck-us.net" <linux@roeck-us.net>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "joel@jms.id.au" <joel@jms.id.au>, "andrew@aj.id.au" <andrew@aj.id.au>, "lee.jones@linaro.org" <lee.jones@linaro.org>, "thierry.reding@gmail.com" <thierry.reding@gmail.com>, "u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>, "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>, "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.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>, "linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>, BMC-SW <BMC-SW@aspeedtech.com>, "garnermic@meta.com" <garnermic@meta.com> Subject: Re: [PATCH 1/3] dt-bindings: Add bindings for aspeed pwm-tach. Date: Thu, 3 Nov 2022 10:36:33 +0000 [thread overview] Message-ID: <2508B515-E153-42C2-B013-2A64A110BCF2@aspeedtech.com> (raw) In-Reply-To: <ee6c5a96-81c4-5729-f623-4b23bc3b8e0a@kernel.org> On 2022/11/3, 5:20 AM, "Krzysztof Kozlowski" <krzk@kernel.org> wrote: On 31/10/2022 06:38, Billy Tsai wrote: > > +patternProperties: > > + "^pwm(@[0-9a-f]+)?$": > > + $ref: ../pwm/aspeed,ast2600-pwm.yaml > Full path, so: /schemas/pwm/aspeed,ast2600-pwm.yaml > Why unit addresses are optional? > > + > > + "^tach(@[0-9a-f]+)?$": > > + $ref: ../hwmon/aspeed,ast2600-tach.yaml > Ditto > Why unit addresses are optional? The pwm_tach is not the bus. I will use pwm: type: object $ref: "/schemas/pwm/aspeed,ast2600-pwm.yaml" tach: type: object $ref: "/schemas/hwmon/aspeed,ast2600-tach.yaml" to replace it. > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/clock/ast2600-clock.h> > > + pwm_tach: pwm_tach@1e610000 { > Node names should be generic. > https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation This is the mfd with pwm and tach, so they are combined as the node name. > No underscores in node names. https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#table-1 I see that the underscore is the valid characters for node names. Did I miss any information? Thanks Best Regards, Billy Tsai _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-03 10:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-31 10:38 [PATCH 0/3] Support pwm/tach driver for aspeed ast26xx Billy Tsai 2022-10-31 10:38 ` Billy Tsai 2022-10-31 10:38 ` [PATCH 1/3] dt-bindings: Add bindings for aspeed pwm-tach Billy Tsai 2022-10-31 10:38 ` Billy Tsai 2022-11-02 21:20 ` Krzysztof Kozlowski 2022-11-02 21:20 ` Krzysztof Kozlowski 2022-11-03 10:36 ` Billy Tsai [this message] 2022-11-03 10:36 ` Billy Tsai 2022-11-03 15:27 ` Krzysztof Kozlowski 2022-11-03 15:27 ` Krzysztof Kozlowski 2022-10-31 10:38 ` [PATCH 2/3] pwm: Add Aspeed ast2600 PWM support Billy Tsai 2022-10-31 10:38 ` Billy Tsai 2022-11-01 11:57 ` kernel test robot 2022-10-31 10:38 ` [PATCH 3/3] hwmon: Add Aspeed ast2600 TACH support Billy Tsai 2022-10-31 10:38 ` Billy Tsai 2022-10-31 16:32 ` Guenter Roeck 2022-10-31 16:32 ` Guenter Roeck 2022-11-02 0:35 ` 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=2508B515-E153-42C2-B013-2A64A110BCF2@aspeedtech.com \ --to=billy_tsai@aspeedtech.com \ --cc=BMC-SW@aspeedtech.com \ --cc=andrew@aj.id.au \ --cc=devicetree@vger.kernel.org \ --cc=garnermic@meta.com \ --cc=jdelvare@suse.com \ --cc=joel@jms.id.au \ --cc=krzk@kernel.org \ --cc=lee.jones@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-aspeed@lists.ozlabs.org \ --cc=linux-hwmon@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pwm@vger.kernel.org \ --cc=linux@roeck-us.net \ --cc=p.zabel@pengutronix.de \ --cc=robh+dt@kernel.org \ --cc=thierry.reding@gmail.com \ --cc=u.kleine-koenig@pengutronix.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.