mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Luis Oliveira <Luis.Oliveira@synopsys.com>,
	wsa@the-dreams.de, robh+dt@kernel.org, mark.rutland@arm.com,
	andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ramiro.Oliveira@synopsys.com, Joao.Pinto@synopsys.com,
	CARLOS.PALMINHA@synopsys.com
Subject: Re: [PATCH v7 3/6] i2c: designware: MASTER mode as separated driver
Date: Wed, 22 Mar 2017 16:47:50 +0200	[thread overview]
Message-ID: <390a6b71-92d4-bafe-224a-f2b2a864cabc@linux.intel.com> (raw)
In-Reply-To: <c224fa537fc1daf9f3256ce7c8da12f73f7035a7.1490007620.git.lolivei@synopsys.com>

On 03/20/17 13:10, Luis Oliveira wrote:
> - The functions related to I2C master mode of operation were transformed
>   in a single driver.
> - Common definitions were moved to i2c-designware-core.h
> - The i2c-designware-core is now only a library file, the functions
>   associated are in a source file called i2c-designware-common and
>   are used by both i2c-designware-master and i2c-designware-slave.
> - To decrease noise in namespace common i2c_dw_*() functions are
>   now using ops to keep them private.
> - Designware PCI driver had to be changed to match the previous ops
>   functions implementation.
>
> Almost all of the "core" source is now part of the "master" source. The
> difference is the functions used by both modes and they are in the
> "common" source file.
>
> Signed-off-by: Luis Oliveira <lolivei@synopsys.com>
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v6-v7
> - Moved kernel doc comments from patch 4/6 to this patch. @Jarkko
> - Fix Designware I2C PCI driver error when looking for previous extern
>   functions.
>
...
>   * struct dw_i2c_dev - private i2c-designware data
> @@ -78,7 +196,11 @@
>   * @acquire_lock: function to acquire a hardware lock on the bus
>   * @release_lock: function to release a hardware lock on the bus
>   * @pm_runtime_disabled: true if pm runtime is disabled
> - *
> + * @dynamic_tar_update_enabled: true if dynamic TAR update is enabled
> + * @disable: function to disable the controller
> + * @disable_int: function to disable all interrupts
> + * @init: function to initialize the I2C hardware
> + *
>   * HCNT and LCNT parameters can be used if the platform knows more accurate
>   * values than the one computed based only on the input clock frequency.
>   * Leave them to be %0 if not used.
> @@ -126,15 +248,31 @@ struct dw_i2c_dev {
>  	int			(*acquire_lock)(struct dw_i2c_dev *dev);
>  	void			(*release_lock)(struct dw_i2c_dev *dev);
>  	bool			pm_runtime_disabled;
> +	void			(*disable)(struct dw_i2c_dev *dev);
> +	void			(*disable_int)(struct dw_i2c_dev *dev);
> +	int			(*init)(struct dw_i2c_dev *dev);
>  };
>
I take my ack back. You are adding comment for 
dynamic_tar_update_enabled which was removed by the 12688dc21f71 
("Revert "i2c: designware: detect when dynamic tar update is possible"")

-- 
Jarkko

  parent reply	other threads:[~2017-03-22 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 11:10 [PATCH v7 0/6] i2c: designware: add I2C SLAVE support Luis Oliveira
2017-03-20 11:10 ` [PATCH v7 1/6] i2c: designware: Cleaning and comment style fixes Luis Oliveira
2017-03-20 11:10 ` [PATCH v7 2/6] i2c: designware: refactoring of the i2c-designware Luis Oliveira
2017-03-20 11:10 ` [PATCH v7 3/6] i2c: designware: MASTER mode as separated driver Luis Oliveira
2017-03-22 14:38   ` Jarkko Nikula
2017-03-22 14:47   ` Jarkko Nikula [this message]
2017-03-22 14:56     ` Luis Oliveira
2017-03-20 11:10 ` [PATCH v7 4/6] i2c: designware: introducing I2C_SLAVE definitions Luis Oliveira
2017-03-22 14:39   ` Jarkko Nikula
2017-03-22 14:53   ` Jarkko Nikula
2017-03-20 11:10 ` [PATCH v7 5/6] i2c: designware: add SLAVE mode functions Luis Oliveira
2017-03-22 15:02   ` Jarkko Nikula
2017-03-20 11:10 ` [PATCH v7 6/6] i2c: designware: enable SLAVE in platform module Luis Oliveira

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=390a6b71-92d4-bafe-224a-f2b2a864cabc@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Luis.Oliveira@synopsys.com \
    --cc=Ramiro.Oliveira@synopsys.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mika.westerberg@linux.intel.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

Powered by JetHome