linux-kernel - Re[12]: [PATCH v3] mfd: syscon: Add non-DT support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1361376371.184258129@f173.mail.ru>
Date:	Wed, 20 Feb 2013 20:06:11 +0400
From:	Alexander Shiyan <shc_work@...l.ru>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Dong Aisheng <dong.aisheng@...aro.org>,
	linux-kernel@...r.kernel.org,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re[12]: [PATCH v3] mfd: syscon: Add non-DT support

> > OK. I can convert platform to DT, no so easy, but possible.
> > But I will use syscon as way to using DT (and MULTIPLATFORM in the future),
> > this mean that I should completely drop ATAG support from this platform
> > (since I cannot use syscon device without DT support, but several platform devices
> > need to use system-wide registers).
> > Arnd, if its OK for you, I will use this way. (I talking about CLPS711X, you know it :) ).
> 
> Ah, I should have realized that this is about clps711x when the patch
> is coming from you ;-)
> 
> This is an existing platform, and I would not require you to move it to
> devicetree just for supporting syscon, although it may be a good idea
> to make that move in the long run.
> 
> For clps711x, we know that there is only one syscon register set, so you
> could do a very simple patch like below. Basically we don't need to

No. Target have a three SYSCON registers and two SYSFLG. All these registers
can be combined into three syscon devices.
Only these registers will be handled via syscon device, so it is not only one.
Or you mean about handle all register via syscon? It is not it.

> treat the absence of DT information as an error, and a call to
> syscon_regmap_lookup_by_compatible or syscon_regmap_lookup_by_phandle
> will always return the syscon device that was registered first, or
> -EPROBE_DEFER for any error.

The initial idea is search desired syscon device from drivers only by one function
(i.e. search syscon device by compatible string or by specific alias) and no depend
on DT or non-DT. I.e. define syscon device always at machine start (even if we run
machine from DTS), because device should be always present in system.

---