This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Mon Jul 4 17:09:11 2022 >From spaans Wed Apr 15 09:50:39 2015 Received: from pop.ziggo.nl [212.54.42.19] by squeeze.vs19.net with POP3 (fetchmail-6.3.21) for (single-drop); Wed, 15 Apr 2015 09:50:39 +0200 (CEST) Received: from md2.tb.mail.iss.local ([212.54.42.152]) by mc5.tb.mail.iss.local (Dovecot) with LMTP id U9M3NrcXLlXjXQAAh0Kp1A for ; Wed, 15 Apr 2015 09:49:32 +0200 Received: from mx24.tb.mail.iss.as9143.net ([212.54.42.152]) by md2.tb.mail.iss.local (Dovecot) with LMTP id WtAVChEoLVWMWwAAH7GgQA ; Wed, 15 Apr 2015 09:51:09 +0200 Received: from vger.kernel.org ([209.132.180.67]) by mx24.tb.mail.iss.as9143.net with esmtp (Exim 4.82) (envelope-from ) id 1YiI4i-0003r6-9i for bmw12-lkml@ziggo.nl; Wed, 15 Apr 2015 09:49:32 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756099AbbDOHtZ (ORCPT ); Wed, 15 Apr 2015 03:49:25 -0400 Received: from mail-pa0-f48.google.com ([209.85.220.48]:34596 "EHLO mail-pa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932442AbbDOHtO (ORCPT ); Wed, 15 Apr 2015 03:49:14 -0400 Received: by pacyx8 with SMTP id yx8so41652054pac.1; Wed, 15 Apr 2015 00:49:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=FWk/Izbu5Q/6XESfZS/Gs+pgu5qzSp+cn6Gemg+sBUs=; b=GJyKpJCK2jbYZM86L5sE8u51ykyp+G375ZQZDe/I7f16xnhWCAZ X-Received: by 10.70.40.164 with SMTP id y4mr43742516pdk.25.1429084154023; Wed, 15 Apr 2015 00:49:14 -0700 (PDT) Received: from localhost.localdomain ([122.169.129.232]) by mx.google.com with ESMTPSA id nw8sm3229329pdb.30.2015.04.15.00.49.09 (version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Apr 2015 00:49:13 -0700 (PDT) From: Sudip Mukherjee To: Jonathan Corbet , Jean Delvare , Wolfram Sang , Willy Tarreau , Greg Kroah-Hartman , One Thousand Gnomes , dan.carpenter@oracle Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org, devel@driverdev.osuosl.org, Sudip Mukherjee Subject: [PATCH 2/4] parport: update TODO and documentation Date: Wed, 15 Apr 2015 13:18:42 +0530 Message-Id: <1429084124-2271-3-git-send-email-sudipm.mukherjee@gmail.com> X-Mailer: git-send-email 1.8.1.2 In-Reply-To: <1429084124-2271-1-git-send-email-sudipm.mukherjee@gmail.com> References: <1429084124-2271-1-git-send-email-sudipm.mukherjee@gmail.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org X-Ziggo-spamsetting: Instelling=Gemiddeld Scorelimiet=14 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.1 cv=Bc50qOZ2 c=1 sm=0 tr=0 a=UK1r566ZdBxH71SXbqIOeA==:17 a=pGLkceISAAAA:8 a=VwQbUJbxAAAA:8 a=cIF5Tx0qAAAA:8 a=1XWaLZrsAAAA:8 a=e9J7MTPGsLIA:10 a=CW_S45dkAAAA:8 a=20KFwNOVAAAA:8 a=W0vUJOdyAAAA:8 a=pap2iGWaTH61xO1dJIsA:9 a=Lq_jYtgmLdasN X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No as parport starts using the device-model, update the documentation to show the newly added functions and update TODO with some other planned modifications. Signed-off-by: Sudip Mukherjee --- Documentation/parport-lowlevel.txt | 49 ++++++++++++++++++++++++++++++++++++++ drivers/parport/TODO-parport | 4 ++++ 2 files changed, 53 insertions(+) diff --git a/Documentation/parport-lowlevel.txt b/Documentation/parport-lowlevel.txt index 120eb20..4c180af 100644 --- a/Documentation/parport-lowlevel.txt +++ b/Documentation/parport-lowlevel.txt @@ -7,9 +7,11 @@ Described here are the following functions: Global functions: parport_register_driver + parport_register_drv parport_unregister_driver parport_enumerate parport_register_device + parport_register_dev parport_unregister_device parport_claim parport_claim_or_block @@ -222,6 +224,26 @@ SEE ALSO parport_unregister_driver, parport_register_device, parport_enumerate + +parport_register_drv - register a device driver with parport +-------------------- + +Everything is same as parport_register_driver, but it will use the device-model +and will register the driver under /sys/bus/parport/driver. Just like +parport_register_driver it will also call the attach callback function but the +differences being attach wil now return its success or error code and the +reference of the driver is also passed to the attach so that it can be used +when calling parport_register_dev. + +static int lp_attach (struct parport *port, struct parport_driver *drv) +{ + ... + private = kmalloc (...); + dev[count++] = parport_register_dev (...); + ... +} + + parport_unregister_driver - tell parport to forget about this driver ------------------------- @@ -442,6 +464,33 @@ SEE ALSO parport_unregister_device, parport_claim + +parport_register_dev - register to use a port +----------------------- + +SYNOPSIS + +#include + +typedef int (*preempt_func) (void *handle); +typedef void (*wakeup_func) (void *handle); +typedef int (*irq_func) (int irq, void *handle, struct pt_regs *); + +struct pardevice *parport_register_dev(struct parport *port, + const char *name, + preempt_func preempt, + wakeup_func wakeup, + irq_func irq, + int flags, + void *handle, + struct parport_driver *drv); + +DESCRIPTION + +It is same as parport_register_device, and it should be only used if your +driver is using the device-model, that is you have registered your driver +using parport_register_drv. + parport_unregister_device - finish using a port ------------------------- diff --git a/drivers/parport/TODO-parport b/drivers/parport/TODO-parport index 089b14e..bdfbf50 100644 --- a/drivers/parport/TODO-parport +++ b/drivers/parport/TODO-parport @@ -17,4 +17,8 @@ Things to be done. 4. A better PLIP (make use of bidirectional/ECP/EPP ports). +5. Show base, irq information in the sys tree. + +6. Module autoloading based on the connected device. + See . -- 1.8.1.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/