public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Annaliese McDermond <nh6z@nh6z.net>,
	eric@anholt.net, f.fainelli@gmail.com, wsa@the-dreams.de,
	swarren@wwwdotorg.org, linux-i2c@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Cc: team@nwdigitalradio.com
Subject: Re: [PATCH v2] i2c: bcm2835: Model Divider in CCF
Date: Tue, 28 May 2019 09:52:21 +0200	[thread overview]
Message-ID: <716a7b8a-c2f8-a3c4-0b3a-be3cb26a6c12@i2se.com> (raw)
In-Reply-To: <20190508071227.18609-1-nh6z@nh6z.net>

Hi Annaliese,

thank you for mention that we have multiple I2C interfaces.

On 08.05.19 09:12, Annaliese McDermond wrote:
> +
> +static struct clk *bcm2835_i2c_register_div(struct device *dev,
> +					const char *mclk_name,
> +					struct bcm2835_i2c_dev *i2c_dev)
> +{
> +	struct clk_init_data init;
> +	struct clk_bcm2835_i2c *priv;
> +	const char *devname = dev_name(dev);
> +
> +	init.ops = &clk_bcm2835_i2c_ops;
> +	init.name = "bcm2835-i2c";

Does this work intentionally in case i2c-0 and i2c-1 are used at the
same time?

Please also check the output of /sys/kernel/debug/clk/clk_summary

Regards
Stefan

  parent reply	other threads:[~2019-05-28  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  7:12 [PATCH v2] i2c: bcm2835: Model Divider in CCF Annaliese McDermond
2019-05-16  5:37 ` Annaliese McDermond
2019-05-16  7:58   ` Wolfram Sang
2019-05-17  1:55     ` Annaliese McDermond
2019-05-27 19:15       ` Wolfram Sang
2019-05-27 20:00         ` Annaliese McDermond
2019-05-27 20:20           ` Wolfram Sang
2019-05-28 22:25           ` Eric Anholt
2019-05-16 10:59 ` Stefan Wahren
2019-05-28  7:52 ` Stefan Wahren [this message]
2019-05-29  3:01   ` Annaliese McDermond
2019-05-29  4:32     ` Annaliese McDermond

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=716a7b8a-c2f8-a3c4-0b3a-be3cb26a6c12@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=nh6z@nh6z.net \
    --cc=swarren@wwwdotorg.org \
    --cc=team@nwdigitalradio.com \
    --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