From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753187AbbCSDYY (ORCPT ); Wed, 18 Mar 2015 23:24:24 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:40070 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750837AbbCSDYX (ORCPT ); Wed, 18 Mar 2015 23:24:23 -0400 Message-ID: <550A4162.8000009@roeck-us.net> Date: Wed, 18 Mar 2015 20:24:18 -0700 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Wolfram Sang CC: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] eeprom: at24: Add support for large EEPROMs connected to SMBus adapters References: <1423067017-27607-1-git-send-email-linux@roeck-us.net> <20150204174723.GB30930@katana> <20150204190819.GA15467@roeck-us.net> <20150204233516.GA1677@katana> <20150205002630.GA396@roeck-us.net> <20150205144028.GA4865@katana> <20150205175326.GA26691@roeck-us.net> <20150212040126.GA1691@roeck-us.net> <20150216120951.GA2840@katana> <20150317042049.GA6765@roeck-us.net> <20150318132707.GD3580@katana> In-Reply-To: <20150318132707.GD3580@katana> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-CTCH-PVer: 0000001 X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-Flags: 0 X-CTCH-RefID: str=0001.0A020201.550A4166.001D,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-Score: 0.001 X-CTCH-ScoreCust: 0.000 X-CTCH-Rules: C_4847, X-CTCH-SenderID: linux@roeck-us.net X-CTCH-SenderID-Flags: 0 X-CTCH-SenderID-TotalMessages: 1 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-TotalRecipients: 0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: mailgid no entry from get_relayhosts_entry X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/18/2015 06:27 AM, Wolfram Sang wrote: > On Mon, Mar 16, 2015 at 09:20:49PM -0700, Guenter Roeck wrote: >> On Mon, Feb 16, 2015 at 01:09:51PM +0100, Wolfram Sang wrote: >>> Hi Guenter, >>> >>>> I wonder where we are with thisp patch; I don't recall a reply to my previous >>>> e-mail. >>> >>> Sorry for the late reply. I needed to recover from a HDD headcrash :( >>> >>>> Do you need some more time to think about it ? Otherwise I'll publish an >>>> out-of-tree version of the at24 driver with the patch applied on github, >>>> for those who might need the functionality provided by this patch. >>> >>> Your last mail made me aware of why we were missing each other before. I >>> see your point now, but yes, still need to think about it. My plan is to >>> have a decision until the 3.21 merge window. >>> >> Hi Wolfram, >> >> any news ? > > Yes :) > > The main misunderstanding we had before was: You were talking about > multi-master safety between transfers, while I was thinking about > multi-master safety between messages. While we need to guarantee this > for the latter, you are right about the former, sadly. True multi-master > safety between transfers is probably like a can of worms currently. > > Still, I think we have a race with your patch when having two read > processes. If b) kicks in after a) has just set the eeprom pointer, a) > will not read the data it wants. For that to prevent, we should take the > adapter_lock during those two transfers needed for the read you > implemented. My preferred solution would be to have __smbus_transfer > like we have __i2c_transfer and then using that. Some mux code could > also make use out of that. But if you are going to use > adapter->algo->smbus_xfer() directly, well, then be it. > You are right, that is a problem. Not for eeprom access itself - that already has a mutex - but for parallel access to the chip through the eeprom file and, say, by i2cdump. I don't call that multi-master, though, so I guess we may have a bit of a terminology problem. I'll see what I can come up with, but I am not sure if I'll find the time before the 4.1 commit window opens. Company has a working solution (kind of), so now I'll have to do this on my own time ;-). Thanks, Guenter