devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Luis Oliveira <Luis.Oliveira@synopsys.com>,
	wsa@the-dreams.de, robh+dt@kernel.org, mark.rutland@arm.com,
	jarkko.nikula@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 v10 5/6] i2c: designware: add SLAVE mode functions
Date: Fri, 09 Jun 2017 11:52:49 +0300	[thread overview]
Message-ID: <1496998369.22624.68.camel@linux.intel.com> (raw)
In-Reply-To: <434489944ec5de13e1ac4e8ad4ab161e22cb718c.1496942505.git.lolivei@synopsys.com>

On Thu, 2017-06-08 at 18:36 +0100, Luis Oliveira wrote:
> - Changes in Kconfig to enable I2C_DESIGNWARE_SLAVE support
> - Slave functions added to core library file
> - Slave abort sources added to common source file
> - New driver: i2c-designware-slave added
> - Changes in the Makefile to compile the I2C_DESIGNWARE_SLAVE module
>   when supported by the architecture.
> 
> All the SLAVE flow is added but it is not enabled via platform
> driver.

> +	} else {
> +		i2c_slave_event(dev->slave, I2C_SLAVE_STOP, &val);
> +		stat = i2c_dw_read_clear_intrbits_slave(dev);
> +	}
> +

> +	//~ if (stat & DW_IC_INTR_TX_OVER)
> +		//~ dw_readl(dev, DW_IC_CLR_TX_OVER);

What is this?

> +
> +	return 1;
> +}

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  parent reply	other threads:[~2017-06-09  8:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 17:36 [PATCH v10 0/6] i2c: designware: add I2C SLAVE support Luis Oliveira
2017-06-08 17:36 ` [PATCH v10 1/6] i2c: designware: Cleaning and comment style fixes Luis Oliveira
2017-06-09  5:12   ` Peter Rosin
     [not found]     ` <5bc3077b-2e4c-eb27-bca1-b7cbfc2dec01-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2017-06-09  7:57       ` Luis Oliveira
2017-06-09  8:38       ` Andy Shevchenko
2017-06-09  8:57         ` Peter Rosin
     [not found] ` <cover.1496942505.git.lolivei-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-06-08 17:36   ` [PATCH v10 2/6] i2c: designware: refactoring of the i2c-designware Luis Oliveira
2017-06-08 17:36 ` [PATCH v10 3/6] i2c: designware: MASTER mode as separated driver Luis Oliveira
2017-06-08 17:36 ` [PATCH v10 4/6] i2c: designware: introducing I2C_SLAVE definitions Luis Oliveira
2017-06-08 17:36 ` [PATCH v10 5/6] i2c: designware: add SLAVE mode functions Luis Oliveira
2017-06-09  6:57   ` kbuild test robot
2017-06-09  8:53     ` Andy Shevchenko
2017-06-09  8:52   ` Andy Shevchenko [this message]
2017-06-08 17:36 ` [PATCH v10 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=1496998369.22624.68.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Luis.Oliveira@synopsys.com \
    --cc=Ramiro.Oliveira@synopsys.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).