From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Chanh Nguyen <chanh@amperemail.onmicrosoft.com>,
Chanh Nguyen <chanh@os.amperecomputing.com>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
Joel Stanley <joel@jms.id.au>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Khanh Pham <khpham@amperecomputing.com>,
linux-arm-kernel@lists.infradead.org,
Thang Nguyen <thang@os.amperecomputing.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Phong Vo <phong@os.amperecomputing.com>,
Conor Dooley <conor+dt@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Open Source Submission <patches@amperecomputing.com>,
Quan Nguyen <quan@os.amperecomputing.com>,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH] ARM: dts: aspeed: Add device tree for Ampere's Mt. Jefferson BMC
Date: Thu, 17 Oct 2024 10:38:26 +1030 [thread overview]
Message-ID: <f833ef3b873d0e71581dd138f046b19fa3fdeaf2.camel@codeconstruct.com.au> (raw)
In-Reply-To: <c42be4ea-9902-4fac-8b1e-afc38fe04bad@amperemail.onmicrosoft.com>
Hi Chanh,
On Wed, 2024-10-16 at 17:26 +0700, Chanh Nguyen wrote:
>
> On 16/10/2024 12:07, Andrew Jeffery wrote:
> > You can also find discussions where other maintainers (Guenter, hwmon
> > maintainer; Krzysztof, devicetree maintainer) have asked that "pmbus"
> > not be used as a compatible:
> >
> > https://lore.kernel.org/all/f76798ea-6edd-4888-8057-c09aaed88f25@roeck-us.net/
> >
>
> Hi Andrew,
> I checked the discussion at
> https://lore.kernel.org/all/f76798ea-6edd-4888-8057-c09aaed88f25@roeck-us.net/
> . It seems the maintainers don't want to use the "pmbus" compatible for
> specific devices. The maintaners require an explicitly compatible from
> device list in drivers/hwmon/pmbus/pmbus.c .
>
There are two problems:
1. Describing your _hardware_ (not drivers) in the devicetree
2. Binding a driver to your device
You ultimately care about both 1 and 2 as you want Linux to do
something useful with the device, but for the purpose of this patch
adding the devicetree, 1 is what matters and 2 is not really a part of
the considerations.
What needs to be the case is that the devicetree describes the device
via an appropriate compatible string for the device (manufacturer and
part number). Prior to that, the compatible string for the device needs
to be documented in a devicetree binding. This may be the trivial-
devices binding if there are no extra properties that need to be
described, or you may need to write your own binding document for the
device if it's more complex and one doesn't yet exist.
So whatever is in pmbus.c needs to be fixed later on if your device is
not yet supported by it, but that's a separate problem (2) to the
problem you have here (1).
Who is the manufacturer and what is the part number?
Andrew
next prev parent reply other threads:[~2024-10-17 0:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 10:50 [PATCH] ARM: dts: aspeed: Add device tree for Ampere's Mt. Jefferson BMC Chanh Nguyen
2024-10-14 10:54 ` Chanh Nguyen
2024-10-14 11:58 ` Krzysztof Kozlowski
2024-10-14 15:02 ` Chanh Nguyen
2024-10-14 14:05 ` Rob Herring (Arm)
2024-10-15 0:44 ` Andrew Jeffery
2024-10-15 6:39 ` Chanh Nguyen
2024-10-16 5:07 ` Andrew Jeffery
2024-10-16 10:26 ` Chanh Nguyen
2024-10-17 0:08 ` Andrew Jeffery [this message]
2024-10-17 10:02 ` Chanh Nguyen
2024-10-18 4:35 ` Andrew Jeffery
2024-10-18 4:34 ` Andrew Jeffery
2024-10-18 10:08 ` Chanh Nguyen
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=f833ef3b873d0e71581dd138f046b19fa3fdeaf2.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=chanh@amperemail.onmicrosoft.com \
--cc=chanh@os.amperecomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=khpham@amperecomputing.com \
--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=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=thang@os.amperecomputing.com \
/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;
as well as URLs for NNTP newsgroup(s).