From: Sebastian Reichel <sre@kernel.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Aaro Koskinen <aaro.koskinen@iki.fi>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: rx51-battery.ko incompatiblity: board code vs DT
Date: Tue, 7 Jul 2015 17:02:30 +0200 [thread overview]
Message-ID: <20150707150230.GB25405@earth> (raw)
In-Reply-To: <201507062144.22911@pali>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Hi,
On Mon, Jul 06, 2015 at 09:44:22PM +0200, Pali Rohár wrote:
> now I found out that rx51-battery.ko driver register sysnode
> /sys/class/power_supply/rx51-battery/ when booting with legacy board
> code. But when booting DT kernel it register sysnode with different name
> /sys/class/power_supply/n900-battery/
>
> Sysfs node for DT kernel comes from Nokia N900 DTS file:
> arch/arm/boot/dts/omap3-n900.dts
>
> I would propose change which change DTS to "rx51-battery" to have it
> compatible with naming which is for legacy board code. It is just
> because to have compatibility and same naming scheme and also to make
> existing programs to work without needing patching them.
>
> What do you think?
Change the driver instead (in rx51_battery_probe):
- di->bat.name = dev_name(&pdev->dev);
+ di->bat.name = "rx51-battery"
This will keep the DT ABI stable and avoid introducing the term rx51
in the device tree file.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-07 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 19:44 rx51-battery.ko incompatiblity: board code vs DT Pali Rohár
2015-07-07 10:41 ` Pavel Machek
2015-07-07 15:02 ` Sebastian Reichel [this message]
2015-07-07 15:15 ` Pali Rohár
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=20150707150230.GB25405@earth \
--to=sre@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=devicetree@vger.kernel.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=tony@atomide.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).