From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastian Hecht Date: Thu, 21 Feb 2013 14:54:06 +0000 Subject: Re: [PATCH] i2c: sh_mobile: Don't start transfers when suspending Message-Id: List-Id: References: <1360862257-10807-1-git-send-email-hechtb+renesas@gmail.com> <20130221091434.GA22806@the-dreams.de> In-Reply-To: <20130221091434.GA22806@the-dreams.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Wolfram Sang Cc: Magnus Damm , linux-sh@vger.kernel.org, linux-i2c@vger.kernel.org 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. Best, Bastian 2013/2/21 Wolfram Sang : > 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastian Hecht Subject: Re: [PATCH] i2c: sh_mobile: Don't start transfers when suspending Date: Thu, 21 Feb 2013 08:54:06 -0600 Message-ID: References: <1360862257-10807-1-git-send-email-hechtb+renesas@gmail.com> <20130221091434.GA22806@the-dreams.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <20130221091434.GA22806@the-dreams.de> Sender: linux-sh-owner@vger.kernel.org To: Wolfram Sang Cc: Magnus Damm , linux-sh@vger.kernel.org, linux-i2c@vger.kernel.org List-Id: linux-i2c@vger.kernel.org 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. Best, Bastian 2013/2/21 Wolfram Sang : > 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 >