public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Markus Probst <markus.probst@posteo.de>
Cc: "Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
	"Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	platform-driver-x86@vger.kernel.org, linux-leds@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v6 2/2] dt-bindings: embedded-controller: Add synology microp devices
Date: Mon, 6 Apr 2026 16:42:56 +0200	[thread overview]
Message-ID: <0b785ee4-7d15-4a9d-a820-20ea15225ea1@kernel.org> (raw)
In-Reply-To: <63fbd1a5cddc5b79302056fa7b01a790aca8ba8e.camel@posteo.de>

On 06/04/2026 16:22, Markus Probst wrote:
> On Mon, 2026-04-06 at 09:59 +0200, Krzysztof Kozlowski wrote:
>> On Sun, Apr 05, 2026 at 07:36:29PM +0200, Markus Probst wrote:
>>> Add the Synology Microp devicetree bindings. Those devices are
>>> microcontrollers found on Synology NAS devices. They are connected to a
>>> serial port on the host device.
>>>
>>> Those devices are used to control certain LEDs, fan speeds, a beeper, to
>>> handle buttons, fan failures and to properly shutdown and reboot the
>>> device.
>>>
>>> This includes the following compatible ids:
>>>  - synology,ds923p-microp
>>>  - synology,ds918p-microp
>>>  - synology,ds214play-microp
>>>  - synology,ds225p-microp
>>>  - synology,ds425p-microp
>>>  - synology,ds710p-microp
>>>  - synology,ds1010p-microp
>>>  - synology,ds723p-microp
>>>  - synology,ds1522p-microp
>>>  - synology,rs422p-microp
>>>  - synology,ds725p-microp
>>>  - synology,ds118-microp
>>>  - synology,ds124-microp
>>>  - synology,ds223-microp
>>>  - synology,ds223j-microp
>>>  - synology,ds1823xsp-microp
>>>  - synology,rs822p-microp
>>>  - synology,rs1221p-microp
>>>  - synology,rs1221rpp-microp
>>>  - synology,ds925p-microp
>>>  - synology,ds1525p-microp
>>>  - synology,ds1825p-microp
>>
>> Drop, we see this in the diff.
> A prior review commit suggested I should add them [1].
> So only synology,ds923p-microp in the Subject then?

I do not see how this list resolves my comment. Really, explain my how
listing part of binding answers WHY they are not compatible?


> 
> [1]
> https://lore.kernel.org/all/20260330-delicate-sassy-mayfly-ebcca7@quoll/
> 
>>
>>>
>>> Signed-off-by: Markus Probst <markus.probst@posteo.de>
>>> ---
>>>  .../synology,ds923p-microp.yaml                    | 112 +++++++++++++++++++++
>>>  MAINTAINERS                                        |   1 +
>>>  2 files changed, 113 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/embedded-controller/synology,ds923p-microp.yaml b/Documentation/devicetree/bindings/embedded-controller/synology,ds923p-microp.yaml
>>> new file mode 100644
>>> index 000000000000..4518e9b74be1
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/embedded-controller/synology,ds923p-microp.yaml
>>> @@ -0,0 +1,112 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/embedded-controller/synology,ds923p-microp.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Synology NAS on-board Microcontroller
>>> +
>>> +maintainers:
>>> +  - Markus Probst <markus.probst@posteo.de>
>>> +
>>> +description: |
>>> +  Synology Microp is a microcontroller found in Synology NAS devices.
>>> +  It is connected to a serial port on the host device.
>>> +
>>> +  It is necessary to properly shutdown and reboot the NAS device and
>>> +  provides additional functionality such as led control, fan speed control,
>>> +  a beeper and buttons on the NAS device.
>>> +
>>> +properties:
>>> +  compatible:
>>> +    enum:
>>> +      - synology,ds923p-microp
>>> +      - synology,ds918p-microp
>>> +      - synology,ds214play-microp
>>> +      - synology,ds225p-microp
>>> +      - synology,ds425p-microp
>>> +      - synology,ds710p-microp
>>> +      - synology,ds1010p-microp
>>> +      - synology,ds723p-microp
>>> +      - synology,ds1522p-microp
>>> +      - synology,rs422p-microp
>>> +      - synology,ds725p-microp
>>> +      - synology,ds118-microp
>>> +      - synology,ds124-microp
>>> +      - synology,ds223-microp
>>> +      - synology,ds223j-microp
>>> +      - synology,ds1823xsp-microp
>>> +      - synology,rs822p-microp
>>> +      - synology,rs1221p-microp
>>> +      - synology,rs1221rpp-microp
>>> +      - synology,ds925p-microp
>>> +      - synology,ds1525p-microp
>>> +      - synology,ds1825p-microp
>>
>> So we already talked about this and you were told to use compatibility.
>> Your driver clearly states several of these are compatible, so I am
>> confused that I do not see it expressed here.
> The driver does not have all functionality implemented yet.

Either this drivers works or not. If it works, explain me how they are
not compatible.

> 
> A few examples of differences not yet visible in the driver:
> - synology,ds214play-microp is the only model in the current list to
> have an cpu fan
> - 4 of the models are arm based and need a different shutdown behaviour
> - different amount of fans (already present in the binding via fan-
> failure-gpios)
> 
> I could try to group them together, but Synology does not document the
> exact difference between them.
> 
> As Rob mentioned [2], I need to be able to handle unexpected
> differences without qurik properties.

I did not object that.


Best regards,
Krzysztof

  reply	other threads:[~2026-04-06 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05 17:36 [PATCH v6 0/2] Introduce Synology Microp driver Markus Probst via B4 Relay
2026-04-05 17:36 ` [PATCH v6 1/2] platform: Add initial synology microp driver Markus Probst via B4 Relay
2026-04-05 17:36 ` [PATCH v6 2/2] dt-bindings: embedded-controller: Add synology microp devices Markus Probst via B4 Relay
2026-04-06  7:59   ` Krzysztof Kozlowski
2026-04-06 14:22     ` Markus Probst
2026-04-06 14:42       ` Krzysztof Kozlowski [this message]
2026-04-06 15:35         ` Markus Probst

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=0b785ee4-7d15-4a9d-a820-20ea15225ea1@kernel.org \
    --to=krzk@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=dakr@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --cc=pavel@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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