linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Bastian Hecht <hechtb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c: sh_mobile: Don't start transfers when suspending
Date: Thu, 21 Feb 2013 10:14:34 +0100	[thread overview]
Message-ID: <20130221091434.GA22806@the-dreams.de> (raw)
In-Reply-To: <CABYn4szejurs2gBVOx_+geOxw13r9KvoShfRiM7OOF5wVvDPLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

  parent reply	other threads:[~2013-02-21  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 17:17 [PATCH] i2c: sh_mobile: Don't start transfers when suspending 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  3:54 ` Magnus Damm
2013-02-18 16:03   ` Bastian Hecht
     [not found]     ` <CABYn4szejurs2gBVOx_+geOxw13r9KvoShfRiM7OOF5wVvDPLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-21  9:14       ` Wolfram Sang [this message]
2013-02-21 14:54         ` Bastian Hecht
     [not found]           ` <CABYn4swuDgTvvyigjnabcg46rcze-DnGhv2Rh7WEFdwkXcHR4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-21 14:59             ` Wolfram Sang
2014-05-21 11:00           ` Wolfram Sang
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=20130221091434.GA22806@the-dreams.de \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=hechtb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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).