From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>, Peter Rosin <peda@axentia.se>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Peter Rosin <peda@axentia.se>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mux: mmio: use reg property when parent device is not a syscon
Date: Mon, 7 Aug 2023 13:26:45 -0500 [thread overview]
Message-ID: <20230807182645.ct2uvkb3s2tuplon@improve> (raw)
In-Reply-To: <b16568ec-0428-981b-01ca-571cc5d52704@ti.com>
On 15:12-20230713, Andrew Davis wrote:
> On 6/5/23 10:41 AM, Andrew Davis wrote:
> > The DT binding for the reg-mux compatible states it can be used when the
> > "parent device of mux controller is not syscon device". It also allows
> > for a reg property. When the reg property is provided, use that to
> > identify the address space for this mux. If not provided fallback to
> > using the parent device as a regmap provider.
> >
> > Signed-off-by: Andrew Davis <afd@ti.com>
> > ---
>
> Ping, still needed and applies cleanly on v6.5-rc1.
>
> Andrew
>
> >
> > Changes from v1:
> > - Flip logic as suggested in v1[0]
> >
> > [0] https://lore.kernel.org/lkml/1c27d9d4-b1cc-c158-90f7-f7e47e02c424@ti.com/T/
> >
> > drivers/mux/mmio.c | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
Reviewed-by: Nishanth Menon <nm@ti.com>
Greg: looks like you were missed in CC
Peter/Greg: Any chance of Looking at this? This is a basic corner stone
for us to clean up much of the mess we have created up in the device
tree syscon nodes and trying to transition those into simple-bus.
> >
> > diff --git a/drivers/mux/mmio.c b/drivers/mux/mmio.c
> > index 44a7a0e885b8d..2c9e4df9d6f2c 100644
> > --- a/drivers/mux/mmio.c
> > +++ b/drivers/mux/mmio.c
> > @@ -44,10 +44,13 @@ static int mux_mmio_probe(struct platform_device *pdev)
> > int ret;
> > int i;
> > - if (of_device_is_compatible(np, "mmio-mux"))
> > + if (of_device_is_compatible(np, "mmio-mux")) {
> > regmap = syscon_node_to_regmap(np->parent);
> > - else
> > - regmap = dev_get_regmap(dev->parent, NULL) ?: ERR_PTR(-ENODEV);
> > + } else {
> > + regmap = device_node_to_regmap(np);
> > + if (IS_ERR(regmap))
> > + regmap = dev_get_regmap(dev->parent, NULL) ?: ERR_PTR(-ENODEV);
> > + }
> > if (IS_ERR(regmap)) {
> > ret = PTR_ERR(regmap);
> > dev_err(dev, "failed to get regmap: %d\n", ret);
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-08-07 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 15:41 [PATCH v2] mux: mmio: use reg property when parent device is not a syscon Andrew Davis
2023-07-13 20:12 ` Andrew Davis
2023-08-07 18:26 ` Nishanth Menon [this message]
2023-08-08 4:36 ` Greg Kroah-Hartman
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=20230807182645.ct2uvkb3s2tuplon@improve \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).