From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Potin Lai <potin.lai.pt@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Patrick Williams <patrick@stwcx.xyz>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Cosmo Chou <cosmo.chou@quantatw.com>,
Potin Lai <potin.lai@quantatw.com>
Subject: Re: [PATCH v3] ARM: dts: aspeed: catalina: Update DTS to support multiple PDB board sources
Date: Mon, 03 Feb 2025 14:18:11 +1030 [thread overview]
Message-ID: <0cbefd2b2488b7855fb374ce94facd9f7440b7a6.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250114-potin-catalina-dts-update-20250102-v3-1-14981744b2fe@gmail.com>
Hi Potin,
On Tue, 2025-01-14 at 14:12 +0800, Potin Lai wrote:
> This patch updates the Catalina device tree to support different
> sources
> of PDB boards.
Can you expand "PDB"?
>
> Changes for Main source PDB board
> - Thermal Sensor Monitoring:
> - Added IOB NIC nodes (TMP421) for thermal sensor monitoring.
Can you expand "IOB"?
> - Added FIO remote thermal node (TMP75) for thermal sensor
> monitoring.
Can you expand "FIO"?
> - Fan Monitoring and Control:
> - Add fan p12V power sensor node (MP5990) for sensor monitoring.
> - Add fan controllers (MAX31790) for fan control and tach
> monitoring.
>
> Changes for 2nd source PDB board
> - Fan Monitoring and Control:
> - Added 2nd source fan controllers (NCT7363) for fan duty control
> and
> tach monitoring.
> - Power Monitoring:
> - Added 2nd source HSC nodes (XDP710) for power sensor monitoring.
> - Address Conflicts:
> - Removed all ina238 nodes due to address conflicts. Moved the
> driver
> probe for ina238 to userspace.
Can you unpack the issue with the conflicts a little further? What was
going on here?
Andrew
prev parent reply other threads:[~2025-02-03 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 6:12 Potin Lai
2025-02-03 3:48 ` Andrew Jeffery [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=0cbefd2b2488b7855fb374ce94facd9f7440b7a6.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=cosmo.chou@quantatw.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=potin.lai.pt@gmail.com \
--cc=potin.lai@quantatw.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®