From: Lee Jones <lee.jones@linaro.org>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: dmitry.torokhov@gmail.com, wens@csie.org, hdegoede@redhat.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@free-electrons.com,
maxime.ripard@free-electrons.com
Subject: Re: [PATCH 2/2] mfd: axp20x: use correct platform device id for many PEK
Date: Tue, 18 Jul 2017 10:49:11 +0100 [thread overview]
Message-ID: <20170718094911.2brtyp2skney72l4@dell> (raw)
In-Reply-To: <2ea34792-3775-7534-3c06-5bf7ca8211c6@free-electrons.com>
On Tue, 18 Jul 2017, Quentin Schulz wrote:
> Hi Lee,
>
> On 18/07/2017 09:19, Lee Jones wrote:
> > On Mon, 17 Jul 2017, Quentin Schulz wrote:
> >
> >> According to their datasheets, the AXP221, AXP223, AXP288, AXP803,
> >> AXP809 and AXP813 PEK have different values for startup time bits from
> >> the AXP20X, let's use the platform device id with the correct values.
> >>
> >> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
> >> ---
> >> drivers/mfd/axp20x.c | 12 ++++++------
> >> 1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > Patch is find, but are these names reference from platform data
> > anywhere i.e. are we going to break anything by applying it?
> >
>
> I don't really understand what you're asking.
Yes, I guess that was a little Fringlish, apologies for my haste.
> We need the first patch of this patch series to be applied before the
> second patch or axp20x-pek driver wouldn't be probed anymore.
>
> There is no Device Tree declaring axp20x-pek and there is no support for
> Device Tree probing in the driver.
>
> I don't see how I could break anything with these patches. Could you
> explain with an abstract example, please? I might not break anything
> here but it's better to know now what I could have broken in another
> situation/with another patch series so I won't make that mistake in the
> future.
>
> Oh, but this patch series would change the name of the directory exposed
> in sysfs (/sys/bus/platform/devices/axp221-pek/*). Is that what you were
> afraid of?
I'm worried about any breakage in terms of name referencing.
If this driver is DT only, then the concern is less, but in the olden
days, we used to conduct device/driver binding using the name. Ergo,
if you change the name in the driver without updating the device
registration, we would not bind and .probe() would not be called.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-07-18 9:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 9:53 [PATCH 0/2] use correct values for startup time bits for AXP22X/AXP8XX PEKs Quentin Schulz
2017-07-17 9:53 ` [PATCH 1/2] Input: axp20x-pek: add support for AXP221 PEK Quentin Schulz
2017-07-17 11:29 ` Maxime Ripard
2017-07-18 7:36 ` Quentin Schulz
2017-07-18 7:57 ` Maxime Ripard
2017-07-18 8:10 ` Quentin Schulz
2017-07-17 9:53 ` [PATCH 2/2] mfd: axp20x: use correct platform device id for many PEK Quentin Schulz
2017-07-18 7:19 ` Lee Jones
2017-07-18 7:43 ` Quentin Schulz
2017-07-18 9:49 ` Lee Jones [this message]
2017-07-18 10:04 ` Quentin Schulz
2017-07-18 10:26 ` Lee Jones
2017-07-18 10:28 ` Lee Jones
2017-07-17 11:15 ` [PATCH 0/2] use correct values for startup time bits for AXP22X/AXP8XX PEKs Quentin Schulz
2017-07-18 7:18 ` Lee Jones
2017-07-18 7:25 ` Quentin Schulz
2017-07-18 7:40 ` Chen-Yu Tsai
2017-07-18 9:53 ` Lee Jones
2017-07-19 7:24 ` Chen-Yu Tsai
2017-07-19 7:46 ` Lee Jones
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=20170718094911.2brtyp2skney72l4@dell \
--to=lee.jones@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=quentin.schulz@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).