From: Vinod <vkoul@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: linux-i2c@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
devicetree@vger.kernel.org, Todor Tomov <todor.tomov@linaro.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: Add binding document for Qualcomm CCI
Date: Mon, 23 Jul 2018 09:24:37 +0530 [thread overview]
Message-ID: <20180723035436.GV3219@vkoul-mobl> (raw)
In-Reply-To: <20180720180318.GA14573@rob-hp-laptop>
On 20-07-18, 12:03, Rob Herring wrote:
> On Tue, Jul 17, 2018 at 06:27:28PM +0530, Vinod Koul wrote:
> > From: Todor Tomov <todor.tomov@linaro.org>
> > +Required properties:
> > + - compatible: Should be one of:
> > + - "qcom,cci-v1.0.8" for 8916;
> > + - "qcom,cci-v1.4.0" for 8996.
>
> It's not very convincing to use version numbers instead of normal SoC
> part# convention when there is a 1-1 mapping.
I was under the impression that we don't have 1-1 mapping. An IP version
is found in multiple SoCs
> > + - #address-cells: Should be <1>.
> > + - #size-cells: Should be <0>.
> > + - reg: Base address of the controller and length of memory mapped region.
> > + - interrupts: Specifier for CCI interrupt.
> > + - clocks: List of clock specifiers, one for each entry in clock-names.
> > + - clock-names: Should contain:
> > + - "mmss_mmagic_ahb" - on 8996 only;
> > + - "camss_top_ahb";
> > + - "cci_ahb";
> > + - "cci";
> > + - "camss_ahb".
> > +
> > +Required properties on 8996:
>
> Rather than '8996', use the compatible string.
Makes sense
> > + - power-domains: Power domain specifier.
> > +
> > +Optional:
> > + - clock-frequency: Desired I2C bus clock frequency in Hz, defaults to 100 kHz
> > + if omitted.
>
> This is the only place that says this block is or has a I2C controller.
> Please make that more explicit (including what ever else this block
> does). I'm guessing there's more given how many clocks and that it has a
> power domain.
Yes this also goes GPIO which will be added after this.
--
~Vinod
next prev parent reply other threads:[~2018-07-23 3:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:57 [PATCH v2 0/2] i2c: Add support for Qualcomm Camera Control Interface Vinod Koul
2018-07-17 12:57 ` [PATCH v2 1/2] dt-bindings: i2c: Add binding document for Qualcomm CCI Vinod Koul
2018-07-20 18:03 ` Rob Herring
2018-07-23 3:54 ` Vinod [this message]
2018-07-23 13:20 ` Rob Herring
2018-07-17 12:57 ` [PATCH v2 2/2] i2c: Add Qualcomm Camera Control Interface driver Vinod Koul
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=20180723035436.GV3219@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=robh@kernel.org \
--cc=todor.tomov@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
/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.