From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754772AbdEDQYk (ORCPT ); Thu, 4 May 2017 12:24:40 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:53773 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752850AbdEDQYC (ORCPT ); Thu, 4 May 2017 12:24:02 -0400 Subject: Re: [PATCH] serdev: Restore serdev_device_write_buf for atomic context To: Johan Hovold , Rob Herring References: <1493380041-14710-1-git-send-email-stefan.wahren@i2se.com> <20170502090638.GB2973@localhost> <20170502131854.GA17710@localhost> Cc: Greg Kroah-Hartman , Jiri Slaby , Sebastian Reichel , Guenter Roeck , Andy Shevchenko , Andrey Smirnov , "linux-serial@vger.kernel.org" , "linux-kernel@vger.kernel.org" From: Stefan Wahren Message-ID: Date: Thu, 4 May 2017 18:22:31 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170502131854.GA17710@localhost> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:U9WKfbYL1dKAvxq4v3zuSuaghNQ6dUiwFcJT1uQLTmXfVAVy+fy 1RAERDX+WOppE5rQF7cNIQILK65xwEcASQnWhKp9X3fNViRKGx+cuIrmoImcN7TgCiRiu26 skuDxRIj0E2SY+Z6+RUZuyLfKqXdxKYJNiL8rV76jML2MRD5P4tM2cj+C+J6xkfHrMmmWH0 kSyb1EewyYbL3+Mv5IeqQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:OLv1AF67Cas=:wG+ODyLe7zqX91Zj5Nj94M qHe39xNWkrW/fU6pyAxF02ju6ZaYRxCWx3AdAYXouPzkXSUFXzZziLJRuEML5efK8hXfYqXRQ 09mFCFcHbR+Cn7XotrEb5shuSxERLpUC0TfZ7anLGL65owRJprCZf5ZKaj1AwMSzsC57s5lf0 j4qbVohWuJJJsChCssMDrdrPkdfNUqztRsPJtupydLTzj4HpdjySmDq1zcAOhBv8458camFoz 1cCRU3RQ3QzlA9o4aN5fsIdPfOegGPbx+oJsvJYrJ/9YO0tC2GghI/t4LiUeWPY4iHDzr4QfT p7pqkG92QkzAaKjKht1L1cXv/o3pA0NIY4DCo9GkGuv7Y4KDF3K8nKhGmqlh9XRnKKdGjxfG+ Nr8RCyDyQ6hG5BrQ5f+CHkatONN8gc+vBl06j1dvWJFj4dAjHZCI/5K/UPp+rdj53PJRObDjz RoSyfZLqKPwVAuE4NYTO3gMnREq0qvxYsY1l4CVEUc+t2/3Fu3fcfo7+bjl2I/4/diI0mvGhI oSAsWcE4PoPilsY20nDZLZvnfCQYWtq4BA5ib1QMuVZxNKZizxV+m6KpblDwWUyfH53SUU4le cE/do8sMZqchfcSqE5M9u182XBfeRjrg8hanjJlQway+SO1CkEDfr7eR913X+tX37b6e3JnpG 71fN+KIF0Z41HlysGvingoVlyM2e9Wc+N73dFD7VXhLyo9nwwJP+J0pUHT41XBd8TuEGH5+di k7bxdk6oYdeyVpqR Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 02.05.2017 um 15:18 schrieb Johan Hovold: > On Tue, May 02, 2017 at 07:41:34AM -0500, Rob Herring wrote: >> On Tue, May 2, 2017 at 4:06 AM, Johan Hovold wrote: >>> On Fri, Apr 28, 2017 at 01:47:21PM +0200, Stefan Wahren wrote: >>>> Starting with commit 6fe729c4bdae ("serdev: Add serdev_device_write >>>> subroutine") the function serdev_device_write_buf cannot be used in >>>> atomic context anymore (mutex_lock is sleeping). So restore the old >>>> behavior. >>> Yeah, preventing use in atomic context seems unnecessary, although any >>> clients writing must now deal with serialisation themselves (as before, >>> and as they should). >> We could just remove the mutex for serdev_device_write and always make >> the client responsible for serialization. > That sounds reasonable. So it's unwanted to have 2 write functions (non-atomic, atomic)? Stefan