From patchwork Tue May 31 14:33:16 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Gustavo F. Padovan" X-Patchwork-Id: 34468 Received: from mail.tu-berlin.de ([130.149.7.33]) by www.linuxtv.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b7kkB-0001tt-D4; Tue, 31 May 2016 14:34:07 +0000 X-tubIT-Incoming-IP: 209.132.180.67 Received: from vger.kernel.org ([209.132.180.67]) by mail.tu-berlin.de (exim-4.84_2/mailfrontend-5) with esmtp id 1b7kk9-0000dp-7e; Tue, 31 May 2016 16:34:07 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754674AbcEaOda (ORCPT + 1 other); Tue, 31 May 2016 10:33:30 -0400 Received: from mail-yw0-f193.google.com ([209.85.161.193]:33955 "EHLO mail-yw0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754329AbcEaOd2 (ORCPT ); Tue, 31 May 2016 10:33:28 -0400 Received: by mail-yw0-f193.google.com with SMTP id j74so19072770ywg.1; Tue, 31 May 2016 07:33:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=e4aFY0CQQd/CEQiAH0ku2MIur6jGWS7StlCGxlYlVUE=; b=BaGbZUVf5v4VzslD6af3IDX5WKtrwtR0hy92R5BFqfewox3uGzJRBeCg8QtKa2iFam 71ECP91MQ2MUPVDr+4w/q9WD2b/aDDA7/SYTb5JIeQ221UEDopJ/FRa6nHS9O+lrVdqk UWLdg1XJhDYx/7v61axxrpe8JwTiLR8KpnEr+68TOUOX8tvIXlb0knIjQpyAx4Q1PtdC LssYTtfvdPszqmEKnAJKhQWwxehEaJX4OvF8AUigQvrsF+9MvVLnXkGdxtU2K64TI7gH A+AWU834JTFYZUyUdfsPhZko5enYeMtMeXTsI5VyveyqzG7iFymb50/eQRKmyX72prZx u8Zw== X-Gm-Message-State: ALyK8tLZWA7EEi5pXGckTodxEFOjx2NhdUXVjCLKvocfbTC/Q1HN9jMXGTZq1K11XEgmLQ== X-Received: by 10.13.243.5 with SMTP id c5mr22556937ywf.40.1464705207701; Tue, 31 May 2016 07:33:27 -0700 (PDT) Received: from jade.localdomain ([201.82.24.203]) by smtp.gmail.com with ESMTPSA id o134sm16522659ywd.53.2016.05.31.07.33.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 May 2016 07:33:27 -0700 (PDT) From: Gustavo Padovan To: Sumit Semwal Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Gustavo Padovan , Dave Jones Subject: [PATCH 2/2] dma-buf/sync_file: improve Kconfig description for Sync Files Date: Tue, 31 May 2016 11:33:16 -0300 Message-Id: <1464705196-24369-2-git-send-email-gustavo@padovan.org> X-Mailer: git-send-email 2.5.5 In-Reply-To: <1464705196-24369-1-git-send-email-gustavo@padovan.org> References: <1464705196-24369-1-git-send-email-gustavo@padovan.org> Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.5.31.142717 X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1600_1699 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, IN_REP_TO 0, LEGITIMATE_NEGATE 0, MSG_THREAD 0, MULTIPLE_RCPTS_RND 0, NO_URI_HTTPS 0, REFERENCES 0, SINGLE_URI_IN_BODY 0, URI_ENDS_IN_HTML 0, __ANY_URI 0, __CP_URI_IN_BODY 0, __HAS_CC_HDR 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HAS_X_MAILING_LIST 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MULTIPLE_RCPTS_CC_X2 0, __REFERENCES 0, __SANE_MSGID 0, __SINGLE_URI_TEXT 0, __SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0, __URI_IN_BODY 0, __URI_NO_WWW 0, __URI_NS , __URI_WITH_PATH 0, __YOUTUBE_RCVD 0' From: Gustavo Padovan We've got a complaint saying that the description was quite obtuse and indeed it was. This patch tries to improve it. Cc: Dave Jones Signed-off-by: Gustavo Padovan --- drivers/dma-buf/Kconfig | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/dma-buf/Kconfig b/drivers/dma-buf/Kconfig index 9824bc4..7e2d2c4 100644 --- a/drivers/dma-buf/Kconfig +++ b/drivers/dma-buf/Kconfig @@ -1,11 +1,20 @@ menu "DMABUF options" config SYNC_FILE - bool "sync_file support for fences" + bool "Explicit Synchronization Framework" default n select ANON_INODES select DMA_SHARED_BUFFER ---help--- - This option enables the fence framework synchronization to export - sync_files to userspace that can represent one or more fences. + The Sync File Framework adds explicit syncronization via + userspace. It enables send/receive 'struct fence' objects to/from + userspace via Sync File fds for synchronization between drivers via + userspace components. It has been ported from Android. + + The first and main user for this is graphics in which a fence is + associated with a buffer. When a job is submitted to the GPU a fence + is attached to the buffer and is transfered via userspace, using Sync + Files fds, to the DRM driver for example. More details at + Documentation/sync_file.txt. + endmenu