From: Florian Fainelli <f.fainelli@gmail.com>
To: Kamal Dasu <kdasu.kdev@gmail.com>,
linux-i2c@vger.kernel.org, wsa@the-dreams.de
Cc: f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com
Subject: Re: [V1, 2/2] dt-bindings: i2c: Update i2c-brcmstb compatible string
Date: Thu, 17 Dec 2015 15:57:51 -0800 [thread overview]
Message-ID: <56734BFF.4000207@gmail.com> (raw)
In-Reply-To: <1450298950-5229-2-git-send-email-kdasu.kdev@gmail.com>
On 16/12/15 12:49, Kamal Dasu wrote:
> Adding compatibility with the DSL and CM SoCs that use
> the "Peripheral" i2c hardware. "brcm,brcmper-i2c" is
> also an allowed string.
>
> Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt b/Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt
> index d6f724e..aeceace 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt
> @@ -2,7 +2,7 @@ Broadcom stb bsc iic master controller
>
> Required properties:
>
> -- compatible: should be "brcm,brcmstb-i2c"
> +- compatible: should be "brcm,brcmstb-i2c" or "brcm,brcmper-i2c"
> - clock-frequency: 32-bit decimal value of iic master clock freqency in Hz
> valid values are 375000, 390000, 187500, 200000
> 93750, 97500, 46875 and 50000
>
--
Florian
next prev parent reply other threads:[~2015-12-17 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 20:49 [V1, 1/2] i2c: brcmstb: Adding support for CM and DSL SoCs Kamal Dasu
2015-12-16 20:49 ` [V1, 2/2] dt-bindings: i2c: Update i2c-brcmstb compatible string Kamal Dasu
2015-12-17 23:57 ` Florian Fainelli [this message]
2015-12-17 23:56 ` [V1, 1/2] i2c: brcmstb: Adding support for CM and DSL SoCs Florian Fainelli
2016-01-03 18:51 ` Wolfram Sang
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=56734BFF.4000207@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).