From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
"Sudeep Holla" <sudeep.holla@arm.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Bill Mills" <bill.mills@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] firmware: arm_ffa: Setup of_node for ffa devices
Date: Tue, 21 Jan 2025 09:59:03 +0000 [thread overview]
Message-ID: <Z49v50epNMm6YvAr@bogus> (raw)
In-Reply-To: <0e863a4baea59865aff0d1b5657f548bc0aa8d2a.1737441631.git.viresh.kumar@linaro.org>
On Tue, Jan 21, 2025 at 12:26:39PM +0530, Viresh Kumar wrote:
> Match and bind the of_node for the FFA device.
I am bit confused and need more details than the above line 😄, because
1. We don't have any binding for FF-A and compatible "arm,ffa" is not yet
defined
2. Even if we have binding, we will not have vm_id and UUID which are
discoverable from the firmware
3. DT maintainers rejected the bindings when it was initially proposed
as it is discoverable. If we need it for a valid reason, we need more
info, this patch doesn't provide full picture to change their stance.
I would like to add minimal binding not for vmid or UUID but for interrupts
only. It is still WIP but I haven't made up my mind on how that should look.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-01-21 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 6:56 [PATCH 0/3] firmware: arm_ffa: Add DT support Viresh Kumar
2025-01-21 6:56 ` [PATCH 1/3] dt-bindings: firmware: Add bindings for ARM FFA Viresh Kumar
2025-01-21 6:56 ` [PATCH 2/3] firmware: arm_ffa: Setup of_node for ffa devices Viresh Kumar
2025-01-21 9:59 ` Sudeep Holla [this message]
2025-01-21 10:09 ` Viresh Kumar
2025-01-24 22:30 ` Rob Herring
2025-01-21 6:56 ` [PATCH 3/3] firmware: arm_ffa: Provide .dma_configure() Viresh Kumar
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=Z49v50epNMm6YvAr@bogus \
--to=sudeep.holla@arm.com \
--cc=alex.bennee@linaro.org \
--cc=bill.mills@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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 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.