From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] spmi-pmic-arb: support configurable number of peripherals
Date: Thu, 15 Oct 2015 11:24:19 -0700 [thread overview]
Message-ID: <20151015182419.GH4558@codeaurora.org> (raw)
In-Reply-To: <8EEAE898-347B-4CEA-BA4D-0C69897E18EB@gmail.com>
On 10/15, Ivan T. Ivanov wrote:
>
> > On Oct 15, 2015, at 1:43 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> >
> > I have to take this back. I missed the part where some pmics are on
> > slave id 2 or slave id 4, so this check isn't going to work. I've
> > adjusted it to use sid % 2 instead and I'll resend these two patches,
> > but I imagine to be more robust we're going to need to add a revid node
> > to the DT under the SID that actually has it. Then we can search the
> > child nodes for a revid compatible node and do the rev probing stuff.
>
> Ah, yes. We don?t use revision information for now.
> I suppose we can just remove these reads until we need
> this information?
>
True, we could just remove all the code and make it look for a
revid node at some later time. But later would be soon because
I'm working on patches to add the read/write/volatile regmap
tables to this driver. I guess I'll just go all the way and do
the revid node part.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-10-15 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 21:54 [PATCH] spmi-pmic-arb: support configurable number of peripherals Stephen Boyd
2015-09-15 1:28 ` Stephen Boyd
2015-09-15 11:20 ` Ivan T. Ivanov
2015-09-15 18:27 ` Stephen Boyd
2015-10-14 22:43 ` Stephen Boyd
2015-10-15 9:23 ` Ivan T. Ivanov
2015-10-15 18:24 ` Stephen Boyd [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=20151015182419.GH4558@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).