mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Anup Patel <apatel@ventanamicro.com>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Jassi Brar" <jassisinghbrar@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Len Brown" <lenb@kernel.org>,
	"Sunil V L" <sunilvl@ventanamicro.com>,
	"Rahul Pathak" <rpathak@ventanamicro.com>,
	"Leyfoon Tan" <leyfoon.tan@starfivetech.com>,
	"Atish Patra" <atish.patra@linux.dev>,
	"Andrew Jones" <ajones@ventanamicro.com>,
	"Samuel Holland" <samuel.holland@sifive.com>,
	"Anup Patel" <anup@brainfault.org>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 05/23] mailbox: Allow controller specific mapping using fwnode
Date: Wed, 11 Jun 2025 18:35:20 +0300	[thread overview]
Message-ID: <aEmiOFwofEJyXm4R@smile.fi.intel.com> (raw)
In-Reply-To: <20250611062238.636753-6-apatel@ventanamicro.com>

On Wed, Jun 11, 2025 at 11:52:20AM +0530, Anup Patel wrote:
> Introduce optional fw_node() callback which allows a mailbox controller
> driver to provide controller specific mapping using fwnode.
> 
> The Linux OF framework already implements fwnode operations for the
> Linux DD framework so the fw_xlate() callback works fine with device
> tree as well.

...

>  struct mbox_chan *mbox_request_channel(struct mbox_client *cl, int index)
>  {
> +	struct fwnode_reference_args fwspec;

Define

	struct fwnode_handle *fwnode;


>  	struct device *dev = cl->dev;

This better to be just a declaration.

>  	struct mbox_controller *mbox;
>  	struct of_phandle_args spec;
>  	struct mbox_chan *chan;
> +	unsigned int i;
>  	int ret;

With the above the below will look like...

> -	if (!dev || !dev->of_node) {
> -		pr_debug("%s: No owner device node\n", __func__);
> +	if (!dev || !dev_fwnode(dev)) {
> +		pr_debug("No owner %s\n", dev ? "fwnode" : "device");
>  		return ERR_PTR(-ENODEV);
>  	}
>  
> -	ret = of_parse_phandle_with_args(dev->of_node, "mboxes", "#mbox-cells",
> -					 index, &spec);
> +	ret = fwnode_property_get_reference_args(dev_fwnode(dev), "mboxes",
> +						 "#mbox-cells", 0, index, &fwspec);
>  	if (ret) {
>  		dev_err(dev, "%s: can't parse \"mboxes\" property\n", __func__);
>  		return ERR_PTR(ret);
>  	}

...this

	dev = cl->dev;
	if (!dev) {
		pr_debug("No owner device\n");
		return ERR_PTR(-ENODEV);
	}

	fwnode = dev_fwnode(dev);
	if (!fwnode) {
		dev_dbg(dev, "No owner fwnode\n");
		return ERR_PTR(-ENODEV);
	}

	ret = fwnode_property_get_reference_args(fwnode, "mboxes",
						 "#mbox-cells", 0, index, &fwspec);
	if (ret) {
		dev_err(dev, "%s: can't parse \"mboxes\" property\n", __func__);

You may save a few bytes by doing it as

		dev_err(dev, "%s: can't parse \"%s\" property\n", __func__, "mboxes");

		return ERR_PTR(ret);
	}

> +	spec.np = to_of_node(fwspec.fwnode);
> +	spec.args_count = fwspec.nargs;
> +	for (i = 0; i < spec.args_count; i++)
> +		spec.args[i] = fwspec.args[i];
> +
>  	scoped_guard(mutex, &con_mutex) {
>  		chan = ERR_PTR(-EPROBE_DEFER);
> -		list_for_each_entry(mbox, &mbox_cons, node)
> -			if (mbox->dev->of_node == spec.np) {
> +		list_for_each_entry(mbox, &mbox_cons, node) {

> +			if (mbox->fw_xlate && dev_fwnode(mbox->dev) == fwspec.fwnode) {

We have a helper device_match_fwnode()

> +				chan = mbox->fw_xlate(mbox, &fwspec);
> +				if (!IS_ERR(chan))
> +					break;
> +			} else if (mbox->of_xlate && mbox->dev->of_node == spec.np) {

No need to check OF node (again). Instead refactor as

			if (device_match_fwnode(...)) {
				if (fw_xlate) {
					...
				} else if (of_xlate) {
					...
				}
			}

>  				chan = mbox->of_xlate(mbox, &spec);
>  				if (!IS_ERR(chan))
>  					break;
>  			}
> +		}
>  
> -		of_node_put(spec.np);
> +		fwnode_handle_put(fwspec.fwnode);
>  
>  		if (IS_ERR(chan))
>  			return chan;


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-06-11 15:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  6:22 [PATCH v5 00/23] Linux SBI MPXY and RPMI drivers Anup Patel
2025-06-11  6:22 ` [PATCH v5 01/23] dt-bindings: mailbox: Add bindings for RPMI shared memory transport Anup Patel
2025-06-11  6:22 ` [PATCH v5 02/23] dt-bindings: mailbox: Add bindings for RISC-V SBI MPXY extension Anup Patel
2025-06-11  6:22 ` [PATCH v5 03/23] RISC-V: Add defines for the SBI message proxy extension Anup Patel
2025-06-11  6:22 ` [PATCH v5 04/23] mailbox: Add common header for RPMI messages sent via mailbox Anup Patel
2025-06-11  6:22 ` [PATCH v5 05/23] mailbox: Allow controller specific mapping using fwnode Anup Patel
2025-06-11 15:35   ` Andy Shevchenko [this message]
2025-06-18  4:08     ` Anup Patel
2025-06-11  6:22 ` [PATCH v5 06/23] mailbox: Add RISC-V SBI message proxy (MPXY) based mailbox driver Anup Patel
2025-06-11  6:22 ` [PATCH v5 07/23] dt-bindings: clock: Add RPMI clock service message proxy bindings Anup Patel
2025-06-11  6:22 ` [PATCH v5 08/23] dt-bindings: clock: Add RPMI clock service controller bindings Anup Patel
2025-06-11 16:16   ` Conor Dooley
2025-06-12  4:00     ` Anup Patel
2025-06-11  6:22 ` [PATCH v5 09/23] clk: Add clock driver for the RISC-V RPMI clock service group Anup Patel
2025-06-11  6:22 ` [PATCH v5 10/23] dt-bindings: Add RPMI system MSI message proxy bindings Anup Patel
2025-06-11  6:22 ` [PATCH v5 11/23] dt-bindings: Add RPMI system MSI interrupt controller bindings Anup Patel
2025-06-11  6:22 ` [PATCH v5 12/23] irqchip: Add driver for the RPMI system MSI service group Anup Patel
2025-06-13 15:33   ` Thomas Gleixner
2025-06-18  5:24     ` Anup Patel
2025-06-13 23:07   ` Atish Patra
2025-06-18  4:50     ` Anup Patel
2025-06-11  6:22 ` [PATCH v5 13/23] ACPI: property: Refactor acpi_fwnode_get_reference_args() Anup Patel
2025-06-11  6:22 ` [PATCH v5 14/23] ACPI: property: Add support for cells property Anup Patel
2025-06-11  6:22 ` [PATCH v5 15/23] ACPI: scan: Update honor list for RPMI System MSI Anup Patel
2025-06-13 23:08   ` Atish Patra
2025-06-11  6:22 ` [PATCH v5 16/23] ACPI: RISC-V: Create interrupt controller list in sorted order Anup Patel
2025-06-11  6:22 ` [PATCH v5 17/23] ACPI: RISC-V: Add support to update gsi range Anup Patel
2025-06-11  6:22 ` [PATCH v5 18/23] ACPI: RISC-V: Add RPMI System MSI to GSI mapping Anup Patel
2025-06-11  6:22 ` [PATCH v5 19/23] irqchip/irq-riscv-imsic-early: Export imsic_acpi_get_fwnode() Anup Patel
2025-06-13 15:34   ` Thomas Gleixner
2025-06-11  6:22 ` [PATCH v5 20/23] mailbox/riscv-sbi-mpxy: Add ACPI support Anup Patel
2025-06-11  6:22 ` [PATCH v5 21/23] irqchip/riscv-rpmi-sysmsi: " Anup Patel
2025-06-13 15:36   ` Thomas Gleixner
2025-06-18  5:08     ` Sunil V L
2025-06-11  6:22 ` [PATCH v5 22/23] RISC-V: Enable GPIO keyboard and event device in RV64 defconfig Anup Patel
2025-06-11  6:22 ` [PATCH v5 23/23] MAINTAINERS: Add entry for RISC-V RPMI and MPXY drivers Anup Patel

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=aEmiOFwofEJyXm4R@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=apatel@ventanamicro.com \
    --cc=atish.patra@linux.dev \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=lenb@kernel.org \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mturquette@baylibre.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=rpathak@ventanamicro.com \
    --cc=samuel.holland@sifive.com \
    --cc=sboyd@kernel.org \
    --cc=sunilvl@ventanamicro.com \
    --cc=tglx@linutronix.de \
    --cc=ukleinek@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®