From: David Lechner <dlechner@baylibre.com>
To: "Erim, Salih" <Salih.Erim@amd.com>,
"Simek, Michal" <michal.simek@amd.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"monstr@monstr.eu" <monstr@monstr.eu>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"git@xilinx.com" <git@xilinx.com>,
"Anand Ashok Dumbre" <anand.ashok.dumbre@xilinx.com>,
"Kadamathikuttiyil Karthikeyan Pillai,
Anish" <anish.kadamathikuttiyil-karthikeyan-pillai@amd.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>, "Rob Herring" <robh@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 1/6] dt-bindings: iio: xilinx: Add Documentation for Sysmon
Date: Fri, 5 Sep 2025 15:44:20 -0500 [thread overview]
Message-ID: <fec12cd9-4709-42ca-b0e5-38f67b63a41c@baylibre.com> (raw)
In-Reply-To: <IA1PR12MB7736D056E505103AC246DC2E9F03A@IA1PR12MB7736.namprd12.prod.outlook.com>
On 9/5/25 9:21 AM, Erim, Salih wrote:
...
>>>
>>>> +
>>>> + xlnx,bipolar:
>>>> + $ref: /schemas/types.yaml#/definitions/flag
>>>> + description:
>>>> + If the supply has a bipolar type and the output will be signed.
>>>
>>> This is very generic. We have it described for ADC channels already
>>> in bindings/iio/adc/adc.yaml. Why can't we use that here?
>>
>> no issue with it.
>> And likely
>> Documentation/devicetree/bindings/iio/adc/xlnx,zynqmp-ams.yaml
>> should deprecated it and start to use new one.
>>
>>
>>
>>> That binding does rely on matching against 'channel' for node names though.
>>> Where a 'type of channel' has been relevant IIRC we've always added a
>>> separate property rather than using the child node name.
>>
>> Is this related to supply/temp channel name?
>>
>> I think one issue with the binding is that current schema allows to define
>> supply@1 and also temp@1
>> but both of them have reg = <1> which is not allowed (duplicate unit-address).
>>
>> Salih: What does this reg value means? Is it physical address where that sensor is
>> placed?
>
> Reg is offset index to offset base of the memory addresses for each. Supplies and temp values
> are located in different offsets.
>
Sounds like the .dts should looks like:
adc@f1270000 {
compatible = "xlnx,versal-sysmon";
reg = <0xf1270000 0x4000>;
...
supply-channels {
#size-cells = <0>;
#address-cells = <1>;
channel@0 {
reg = <0>;
label = "vccint";
};
...
};
temperature-channels {
#size-cells = <0>;
#address-cells = <1>;
channel@0 {
reg = <0>;
label = "aie-temp-ch0";
};
...
};
};
next prev parent reply other threads:[~2025-09-05 20:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 8:41 [PATCH 0/6] xilinx: Add support for Xilinx Sysmon IP Michal Simek
2025-09-05 8:41 ` [PATCH 1/6] dt-bindings: iio: xilinx: Add Documentation for Sysmon Michal Simek
2025-09-05 11:30 ` Jonathan Cameron
2025-09-05 12:29 ` Michal Simek
2025-09-05 14:21 ` Erim, Salih
2025-09-05 20:44 ` David Lechner [this message]
2025-09-07 10:51 ` Jonathan Cameron
2025-09-08 11:13 ` Erim, Salih
2025-09-05 8:41 ` [PATCH 2/6] iio: versal-sysmon: add driver for Versal Sysmon Michal Simek
2025-09-05 12:23 ` Jonathan Cameron
2025-09-09 10:33 ` Andy Shevchenko
2025-09-10 8:26 ` Michal Simek
2025-09-05 8:41 ` [PATCH 3/6] iio: adc: versal-sysmon: Support AI Engine thermal monitoring Michal Simek
2025-09-05 8:41 ` [PATCH 4/6] dt-bindings: thermal: versal: Add description for Versal Thermal Michal Simek
2025-09-05 18:30 ` Conor Dooley
2025-09-08 6:39 ` Michal Simek
2025-09-05 8:41 ` [PATCH 5/6] thermal: versal-thermal: Add Versal thermal driver Michal Simek
2025-09-05 8:41 ` [PATCH 6/6] thermal: versal-thermal: Support thermal management in AI Engine Michal Simek
2025-09-05 10:48 ` Krzysztof Kozlowski
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=fec12cd9-4709-42ca-b0e5-38f67b63a41c@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Salih.Erim@amd.com \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=andy@kernel.org \
--cc=anish.kadamathikuttiyil-karthikeyan-pillai@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nuno.sa@analog.com \
--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
all inboxes | Powered by JetHome®