From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Jassi Brar <jassisinghbrar@gmail.com>
Subject: Re: [PATCH v2 2/2] i2c: add support for Socionext SynQuacer I2C controller
Date: Mon, 26 Feb 2018 20:18:04 +0200 [thread overview]
Message-ID: <CAHp75VdFkdQp++z2nN2+cnSeq65YUoBq04tykZfBeun-5deDSA@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu9qc=h1mC=6CHiu5aX0NSjLgzahyQ1xdRWo5ZYwcDir1Q@mail.gmail.com>
On Mon, Feb 26, 2018 at 7:51 PM, Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> On 26 February 2018 at 17:16, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> Perhaps we could agree on the binding first? Currently, I have the following
>
> Device (I2C0) {
> Name (_HID, "SCX0003")
> Name (_UID, Zero)
> Name (_CRS, ResourceTemplate () {
> Memory32Fixed (ReadWrite, SYNQUACER_I2C1_BASE, SYNQUACER_I2C1_SIZE)
> Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive) { 197 }
> })
>
> Name (_DSD, Package () // _DSD: Device-Specific Data
> {
> ToUUID ("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> Package () {
> Package (2) { "socionext,pclk-rate", 62500000 },
> }
> })
>
> and I don't intend to add 'clock-frequency' here because it would be
> redundant anyway.
Right.
> Does this look sane?
I can't say about property name, but otherwise yes.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2018-02-26 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 19:16 [PATCH v2 0/2]add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-02-22 19:16 ` [PATCH v2 1/2] dt-bindings: i2c: add binding for Socionext SynQuacer I2C Ard Biesheuvel
2018-02-22 19:16 ` [PATCH v2 2/2] i2c: add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-02-23 12:27 ` Andy Shevchenko
2018-02-23 12:40 ` Ard Biesheuvel
2018-02-23 13:12 ` Andy Shevchenko
2018-02-26 9:59 ` Ard Biesheuvel
2018-02-26 11:35 ` Andy Shevchenko
2018-02-26 14:58 ` Ard Biesheuvel
2018-02-26 17:05 ` Andy Shevchenko
2018-02-26 17:16 ` Ard Biesheuvel
2018-02-26 17:51 ` Ard Biesheuvel
2018-02-26 18:18 ` Andy Shevchenko [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=CAHp75VdFkdQp++z2nN2+cnSeq65YUoBq04tykZfBeun-5deDSA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).