From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Rob Herring (Arm)" <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Len Brown <lenb@kernel.org>, Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH v3] of: property: Increase NR_FWNODE_REFERENCE_ARGS
Date: Mon, 10 Feb 2025 17:34:44 +0200 [thread overview]
Message-ID: <Z6oclML_DC1Vnf6z@smile.fi.intel.com> (raw)
In-Reply-To: <20250210-fix_arg_count-v3-1-a084a5013008@quicinc.com>
On Mon, Feb 10, 2025 at 11:00:32PM +0800, Zijun Hu wrote:
> From: Zijun Hu <quic_zijuhu@quicinc.com>
>
> Currently, the following two macros have different values:
>
> // The maximal argument count for firmware node reference
> #define NR_FWNODE_REFERENCE_ARGS 8
> // The maximal argument count for DT node reference
> #define MAX_PHANDLE_ARGS 16
>
> It may cause firmware node reference's argument count out of range if
> directly assign DT node reference's argument count to firmware's.
>
> drivers/of/property.c:of_fwnode_get_reference_args() is doing the direct
> assignment, so may cause firmware's argument count @args->nargs got out
> of range, namely, in [9, 16].
>
> Fix by increasing NR_FWNODE_REFERENCE_ARGS to 16 to meet DT requirement.
...
> -#define NR_FWNODE_REFERENCE_ARGS 8
> +#define NR_FWNODE_REFERENCE_ARGS 16
Thinking of the case, perhaps you also want
static_assert(NR_FWNODE_REFERENCE_ARGS == MAX_PHANDLE_ARGS);
to be put somewhere, but I don't think we can do it in this header file.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-10 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:00 [PATCH v3] of: property: Increase NR_FWNODE_REFERENCE_ARGS Zijun Hu
2025-02-10 15:34 ` Andy Shevchenko [this message]
2025-02-11 12:20 ` Zijun Hu
2025-02-11 12:24 ` Andy Shevchenko
2025-02-11 13:40 ` Zijun Hu
2025-02-11 14:22 ` Rob Herring
2025-02-11 14:57 ` Zijun Hu
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=Z6oclML_DC1Vnf6z@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=saravanak@google.com \
--cc=zijun_hu@icloud.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).