linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Austin Christ <austinwc@codeaurora.org>,
	wsa@the-dreams.de, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	timur@codeaurora.org, rruigrok@codeaurora.org,
	nkaje@codeaurora.org, cov@codeaurora.org
Subject: Re: [PATCH v4 1/2] i2c: qup: add ACPI support
Date: Wed, 08 Jun 2016 23:02:00 +0200	[thread overview]
Message-ID: <4749471.m1cxc4jj96@wuerfel> (raw)
In-Reply-To: <1465409985-17113-1-git-send-email-austinwc@codeaurora.org>

On Wednesday, June 8, 2016 12:19:44 PM CEST Austin Christ wrote:
> +               ret = device_property_read_u32(qup->dev,
> +                               "src-clock-hz", &src_clk_freq);
> +               if (ret) {
> +                       dev_warn(qup->dev, "using default src-clock-hz %d",
> +                               DEFAULT_SRC_CLK);
> +                       src_clk_freq = DEFAULT_SRC_CLK;
> +               }
> 

Where is this property documented?

	Arnd

  parent reply	other threads:[~2016-06-08 21:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 18:19 [PATCH v4 1/2] i2c: qup: add ACPI support Austin Christ
2016-06-08 18:19 ` [PATCH v4 2/2] i2c: qup: support SMBus block read Austin Christ
2016-06-18 14:13   ` Wolfram Sang
2016-06-08 21:02 ` Arnd Bergmann [this message]
2016-06-30 11:35   ` [PATCH v4 1/2] i2c: qup: add ACPI support Christopher Covington
2016-06-30 11:52     ` Arnd Bergmann
2016-06-30 18:50       ` Christopher Covington
2016-07-01  9:57         ` Arnd Bergmann
2016-06-09 13:51 ` kbuild test robot
2016-06-18 14:10 ` Wolfram Sang
2016-06-20  8:24   ` Mika Westerberg
2016-06-20 15:00     ` Timur Tabi
2016-06-20 15:07       ` Mika Westerberg

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=4749471.m1cxc4jj96@wuerfel \
    --to=arnd@arndb.de \
    --cc=austinwc@codeaurora.org \
    --cc=cov@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkaje@codeaurora.org \
    --cc=rruigrok@codeaurora.org \
    --cc=timur@codeaurora.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).