linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Ajay Gupta <ajayg@nvidia.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Peter Rosin <peda@axentia.se>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: [v12,1/2] i2c: buses: add i2c bus driver for NVIDIA GPU
Date: Mon, 1 Oct 2018 21:37:28 +0200	[thread overview]
Message-ID: <20181001193727.GA1900@kunai> (raw)

On Mon, Oct 01, 2018 at 07:33:02PM +0000, Ajay Gupta wrote:
> Hi Heikki and Peter,
> 
> > > > > Can we get the working set in while the issues is being debugged?
> > > >
> > > > I'm not the one making the decision, and I don't even know if this
> > > > is going through the i2c or the usb tree? If it's going through the
> > > > i2c tree you need a tag from the usb people (Greg?) on patch 2/2,
> > > > and if it's going through the usb tree, you need a tag from Wolfram
> > > > on patch 1/2. As I said, I'm not involved with that part, I'm just
> > > > reviewing these patches because I felt like it.
> > > >
> > > > The remaining issue that bothers me is the looping reads, and your
> > > > email address reveals that you should be in a very good position to
> > > > work out why they do not work, and fix it or let us know why they
> > > > don't.
> > I am working with different teams to debug this and I think it may take some
> > time to know the root cause.
> We got confirmation from HW team about 4 byte read limitation. There has to
> be a STOP after every single read cycle. One read cycle supports maximum of
> 4 byte burst. I will update the patches with a comment on this.

Could it be that this is more an SMBus controller than an I2C
controller? I haven't looked at the specs but maybe populating
smbus_xfer instead of master_xfer is an option here?

             reply	other threads:[~2018-10-01 19:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 19:37 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-24 19:44 [v12,1/2] i2c: buses: add i2c bus driver for NVIDIA GPU Greg Kroah-Hartman
2018-10-24 17:46 Ajay Gupta
2018-10-16 23:21 Wolfram Sang
2018-10-16 17:46 Peter Rosin
2018-10-02 16:34 Ajay Gupta
2018-10-02  7:27 Wolfram Sang
2018-10-01 22:04 Ajay Gupta
2018-10-01 21:16 Ajay Gupta
2018-10-01 19:51 Peter Rosin
2018-10-01 19:33 Ajay Gupta
2018-09-13 23:32 Ajay Gupta
2018-09-13 11:11 Heikki Krogerus
2018-09-13  7:36 Peter Rosin
2018-09-12 22:22 Ajay Gupta
2018-09-12 21:57 Peter Rosin
2018-09-12 18:02 Ajay Gupta
2018-09-12 11:02 Peter Rosin
2018-09-12 10:25 Peter Rosin
2018-09-11 22:48 Ajay Gupta
2018-09-11 20:57 Peter Rosin
2018-09-11 17:45 Ajay Gupta

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=20181001193727.GA1900@kunai \
    --to=wsa@the-dreams.de \
    --cc=ajayg@nvidia.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peda@axentia.se \
    /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).