From: Stanimir Varbanov <svarbanov@mm-sol.com>
To: Courtney Cavin <courtney.cavin@sonymobile.com>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"Ivan T. Ivanov" <iivanov@mm-sol.com>,
Josh Cartwright <joshc@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [RFC PATCH 0/6] Support for QPNP PMIC's
Date: Wed, 25 Jun 2014 14:07:13 +0300 [thread overview]
Message-ID: <53AAAD61.3020605@mm-sol.com> (raw)
In-Reply-To: <20140624223604.GB10905@sonymobile.com>
Hi Courtney,
Thanks for the comments.
On 06/25/2014 01:36 AM, Courtney Cavin wrote:
> On Fri, Jun 20, 2014 at 02:21:19PM +0200, Stanimir Varbanov wrote:
>> Hello to all,
>>
>> The goal of this WIP set is to provide support for sub-functional
>> hw blocks inside Qualcomm QPNP PMIC chips by creating a new qpnp
>> bus (device-driver modeled). On SPMI interface we attach a so called
>> Slaves. For example one PMIC chip like pm8941 has two slave id's. On
>> every slaveid the PMIC chip has various peripherials. Every peripheral
>> driver should expose qpnp_driver structure and implement the .probe
>> and .remove callbacks. Every peripheral driver will reside on the
>> proper place in /drivers directory.
>>
>> The fisrt patch describes the devicetree binding of the slave devices
>> attached to the SPMI interface. The second patch adds implemetation of
>> the qpnp-bus and a layer connection with the SPMI interface. The third
>> patch adds spmi arbiter and underlying slaveid devicetree nodes for
>> msm8974 SoC. The other patches are example of rtc-qpnp driver and
>> binding documentation.
>>
>> Since this set is a WIP, it will be used as a starting point for future
>> duscussions about implementing QPNP PMIC sub-function hw blocks.
>
> Ok. I have a few critical problems with this approach to implementing
> support for the PMICs:
> - It's *way* more code than needed if done with of_platform_populate()
Agreed, but this will be the price we must pay to keep architectural
correctness. The PMIC peripherals are not directly accessible by the CPU
bus and thus they shouldn't be treated as platform devices. That fact
gives as an opportunity to create a qpnp bus on which we will attach the
whole bunch of PMIC peripherals and using DT we can describe register
regions (256B each) belonging to it.
> - AFAICT, the only direct relation between this and 'QPNP' is the 256
> byte block size, which I would argue can be clearly expressed in DT
> instead with #size-cells == 1, and #address-cells == 1
The QPNP schema is a private case of Qualcomm PMIC's, so generalising
will over-engineering IMO.
> - The resource code from drivers/{base,of}/platform.c is reimplemented
> here, without any added benefit
The resource code could be simplified to satisfy our needs.
--
regards,
Stan
next prev parent reply other threads:[~2014-06-25 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 12:21 [RFC PATCH 0/6] Support for QPNP PMIC's Stanimir Varbanov
2014-06-20 12:21 ` [RFC PATCH 1/6] dt: qpnp: add binding description of Qualcomm QPNP PMICs Stanimir Varbanov
2014-06-20 12:21 ` [RFC PATCH 2/6] qpnp: add support for " Stanimir Varbanov
2014-06-20 12:21 ` [RFC PATCH 3/6] dt: qcom: msm8974: add qpnp-spmi device nodes Stanimir Varbanov
2014-06-20 12:21 ` [RFC PATCH 4/6] rtc: add qpnp rtc driver Stanimir Varbanov
2014-06-20 12:21 ` [RFC PATCH 5/6] dt: msm8974: add qpnp rtc device node Stanimir Varbanov
2014-06-20 12:21 ` [RFC PATCH 6/6] dt: rtc: add binding document for rtc-qpnp Stanimir Varbanov
2014-06-24 22:36 ` [RFC PATCH 0/6] Support for QPNP PMIC's Courtney Cavin
2014-06-25 11:07 ` Stanimir Varbanov [this message]
2014-06-25 18:04 ` Courtney Cavin
2014-06-25 21:18 ` Rob Herring
2014-06-25 21:28 ` Courtney Cavin
2014-06-26 15:12 ` Stanimir Varbanov
2014-06-26 15:48 ` Stanimir Varbanov
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=53AAAD61.3020605@mm-sol.com \
--to=svarbanov@mm-sol.com \
--cc=courtney.cavin@sonymobile.com \
--cc=iivanov@mm-sol.com \
--cc=joshc@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.