All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Bastian Hecht <hechtb@gmail.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: sh_mobile: Don't start transfers when suspending
Date: Wed, 21 May 2014 11:00:19 +0000	[thread overview]
Message-ID: <20140521110019.GS2708@katana> (raw)
In-Reply-To: <CABYn4swuDgTvvyigjnabcg46rcze-DnGhv2Rh7WEFdwkXcHR4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On Thu, Feb 21, 2013 at 08:54:06AM -0600, Bastian Hecht wrote:
> Hi Wolfram,
> 
> oh yes I can gladly do so. To make a realistic estimation it might
> take a few weeks until I find time for it though. If we can wait so
> long, count on me.

Ping. Still interested?

> 
> Best,
> 
>  Bastian
> 
> 2013/2/21 Wolfram Sang <wsa@the-dreams.de>:
> > Hi Bastian,
> >
> >> > Also, do you know the reason why this isn't handled in the i2c layer
> >> > by default? I ask because your comment mentions that i2c-tegra.c does
> >> > the same thing and I can't see anything in this patch that is actually
> >> > related to our I2C hardware.
> >>
> >> Yes, many drivers have a similar scheme and to me it more looked like
> >> all drivers need to take care about this case unrelated to different
> >> hardware. So the question arises if this can't be handled in the core
> >> - or if I get something wrong here.
> >
> > I don't see any reason why this couldn't be handled in the core. If you
> > want to have a take on this issue (after the other bug is fixed), this
> > will be highly appreciated.
> >
> > Thanks,
> >
> >    Wolfram
> >

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Bastian Hecht <hechtb@gmail.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: sh_mobile: Don't start transfers when suspending
Date: Wed, 21 May 2014 13:00:19 +0200	[thread overview]
Message-ID: <20140521110019.GS2708@katana> (raw)
In-Reply-To: <CABYn4swuDgTvvyigjnabcg46rcze-DnGhv2Rh7WEFdwkXcHR4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On Thu, Feb 21, 2013 at 08:54:06AM -0600, Bastian Hecht wrote:
> Hi Wolfram,
> 
> oh yes I can gladly do so. To make a realistic estimation it might
> take a few weeks until I find time for it though. If we can wait so
> long, count on me.

Ping. Still interested?

> 
> Best,
> 
>  Bastian
> 
> 2013/2/21 Wolfram Sang <wsa@the-dreams.de>:
> > Hi Bastian,
> >
> >> > Also, do you know the reason why this isn't handled in the i2c layer
> >> > by default? I ask because your comment mentions that i2c-tegra.c does
> >> > the same thing and I can't see anything in this patch that is actually
> >> > related to our I2C hardware.
> >>
> >> Yes, many drivers have a similar scheme and to me it more looked like
> >> all drivers need to take care about this case unrelated to different
> >> hardware. So the question arises if this can't be handled in the core
> >> - or if I get something wrong here.
> >
> > I don't see any reason why this couldn't be handled in the core. If you
> > want to have a take on this issue (after the other bug is fixed), this
> > will be highly appreciated.
> >
> > Thanks,
> >
> >    Wolfram
> >

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-05-21 11:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 16:18 [PATCH] i2c: sh_mobile: Don't start transfers when suspending Bastian Hecht
2013-02-14 17:17 ` Bastian Hecht
     [not found] ` <1360862257-10807-1-git-send-email-hechtb+renesas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-02-16  2:26   ` Simon Horman
2013-02-16  2:26     ` Simon Horman
2013-02-16  3:54 ` Magnus Damm
2013-02-16  3:54   ` Magnus Damm
2013-02-18 16:03   ` Bastian Hecht
2013-02-18 16:03     ` Bastian Hecht
     [not found]     ` <CABYn4szejurs2gBVOx_+geOxw13r9KvoShfRiM7OOF5wVvDPLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-21  9:14       ` Wolfram Sang
2013-02-21  9:14         ` Wolfram Sang
2013-02-21 14:54         ` Bastian Hecht
2013-02-21 14:54           ` Bastian Hecht
     [not found]           ` <CABYn4swuDgTvvyigjnabcg46rcze-DnGhv2Rh7WEFdwkXcHR4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-21 14:59             ` Wolfram Sang
2013-02-21 14:59               ` Wolfram Sang
2014-05-21 11:00           ` Wolfram Sang [this message]
2014-05-21 11:00             ` Wolfram Sang
2014-06-24  8:14             ` Bastian Hecht
2014-06-24  8:14               ` Bastian Hecht

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=20140521110019.GS2708@katana \
    --to=wsa@the-dreams.de \
    --cc=hechtb@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.