[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfaOfBZYjQa960keORW=VjOn2PdwoYpJMG7SsN83daSJg@mail.gmail.com>
Date: Thu, 30 Jan 2020 17:34:15 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Suman Anna <s-anna@...com>
Cc: Lee Jones <lee.jones@...aro.org>, Arnd Bergmann <arnd@...db.de>,
David Lechner <david@...hnology.com>,
Tony Lindgren <tony@...mide.com>,
Roger Quadros <rogerq@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: [PATCH v2] mfd: syscon: Use a unique name with regmap_config
On Tue, Jan 28, 2020 at 1:14 AM Suman Anna <s-anna@...com> wrote:
>
> The DT node full name is currently being used in regmap_config
> which in turn is used to create the regmap debugfs directories.
> This name however is not guaranteed to be unique and the regmap
> debugfs registration can fail in the cases where the syscon nodes
> have the same unit-address but are present in different DT node
> hierarchies. Replace this logic using the syscon reg resource
> address instead (inspired from logic used while creating platform
> devices) to ensure a unique name is given for each syscon.
> - syscon_config.name = of_node_full_name(np);
> + syscon_config.name = kasprintf(GFP_KERNEL, "%pOFn@...x", np,
> + (u64)res.start);
Explicit castings in printf() usually tell us that something is not okay.
Yes, for resource_size_t we have %pa.
On top of that, I would rather see %pfwn to avoid modification for
other fwnode types.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists