Hey Bjorn-
On Sat, Oct 05, 2013 at 11:11:36PM -0700, Bjorn Andersson wrote:
> On Tue, Aug 27, 2013 at 2:55 PM, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote:
> > On 08/27/2013 11:01 AM, Josh Cartwright wrote:
> > ...
> > cell 0 - address type (0: master, 1: unique ID, 2: group ID, ...)
>
> I think it would make sense to have the master id as a property of the
> bus,
Except that SPMI supports bus configurations with multiple masters.
Unless by 'bus' you meant 'bus controller' here?
> as you could consider this to indicate different buses and then
> usid, gsid and base being part of the reg.
>
> > cell 1 - address value
>
> I did hack up Josh patchset to read a reg touple of <usid, base>
> instead of just usid. I stored the second value in the spmi_device
> struct for easy access, but maybe it should be done like on
> codeaurora; in a resource?
> I believe this looks nice, but as I haven't read the mipi spec I
> wonder, will there be a case where you don't have an offset/base?
> Should it just be made optional?
The SPMI spec says nothing about partitioning up the slave address to
support multiple functions. AFAICT, this is a Qualcomm-created
construct (QPNP) for the 8x41 PMICs. It's difficult to tell at this
point whether or not other vendors might implement a similarly
partitioned scheme.
I suspect the intent is that implementations make use of logical slave
ID for each function in a multi-function device.
> Can we make the address <usid, [base]> and have the code populate a
> resource based on a reg-names property? That way it would be possible
> to extend it to support gsid in case we want to (would require
> reg-names though).
It is certainly possible, and, as you've seen, is how the current
codeaurora.org tree implements SPMI. But, I'm actually actively trying
to avoid doing so, as it conflates Qualcomm-implementation details and
what is actually in the spec (and not just the address space
partitioning, but also the of_spmi.c[2] parsing must know about
interrupts, which are _also_ completely outside the SPMI spec).
Instead what I hope to do for v3 is either:
A) Make QPNP its own bus type (for which I have a prototyped
implementation). A PMIC driver sits on the SPMI bus and registers
itself as a QPNP controller. QPNP controllers have very
simple 8-bit register read/write operations used by QPNP devices.
B) Effectively the same as A, but gets rid of a special QPNP bus type
and uses mfd/platform devices, similar to other in-tree PMIC drivers
(currently working on prototyping this approach)
> With the hack to Josh's patchset I quickly ported qpnp-revision and
> qpnp-vibrator, and it seems to work quite nicely.
Great! Thanks for testing.
Josh
1: https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/drivers/spmi
2: https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/drivers/of/of_spmi.c
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
