From: David Collins <collinsd@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] spmi: prefix spmi bus device names with "spmi"
Date: Tue, 13 Oct 2020 17:59:44 -0700 [thread overview]
Message-ID: <79326f1b-cd0a-50c2-db11-8b5a0f711cd3@codeaurora.org> (raw)
In-Reply-To: <160167477566.310579.12040108464021349450@swboyd.mtv.corp.google.com>
On 10/2/20 2:39 PM, Stephen Boyd wrote:
> I see things like this on my console:
>
> [ 1.684617] spmi spmi-0: PMIC arbiter version v5 (0x50000000)
>
> and 'spmi' is the bus name I'm thinking about. But I think that's
> because there isn't a driver attached. Nothing prints for the 0-00
> device by default, so I enabled the debug print for it and I see
>
> [ 1.693280] pmic-spmi 0-00: 28: unknown v2.0
>
> Anyway, the device name was written to follow i2c as far as I can tell.
>
> If scripts, i.e. computers, have a hard time figuring out the name of
> the device then fix the script?
I agree that we can drop this patch. There is no technical requirement
for the spmi device naming scheme to be changed. We will update our
downstream test scripts to use the upstream naming scheme and also
socialize the naming difference internally.
Take care,
David
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2020-10-14 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 22:04 [RESEND PATCH] spmi: prefix spmi bus device names with "spmi" David Collins
2020-10-01 0:07 ` Stephen Boyd
2020-10-01 17:43 ` Mark Brown
2020-10-01 18:51 ` Stephen Boyd
2020-10-02 0:45 ` David Collins
2020-10-02 16:03 ` Mark Brown
2020-10-02 17:48 ` Stephen Boyd
2020-10-02 18:04 ` Mark Brown
2020-10-02 21:39 ` Stephen Boyd
2020-10-14 0:59 ` David Collins [this message]
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=79326f1b-cd0a-50c2-db11-8b5a0f711cd3@codeaurora.org \
--to=collinsd@codeaurora.org \
--cc=broonie@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.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).