Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1126769ybe; Wed, 11 Sep 2019 09:46:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqwVhc/3i75BOeilTc5qk2hrLlqZT3If+fswnz9zDF7u2Uf3XHMyeDn3NFlb0fsEnL0ZsKo7 X-Received: by 2002:a05:6402:1685:: with SMTP id a5mr25734856edv.304.1568220403559; Wed, 11 Sep 2019 09:46:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568220403; cv=none; d=google.com; s=arc-20160816; b=MP9xbIB5LTAkkZ514YfQ5fVZy3o0X21wB703z1zsftWY2Q3+nBw9rwyeYgT33tszV4 lazlRgZ8Htqpt6gFBbzx3XEGcu0G8q3ENBsnmo62HK8TcSYJ+DLWjzbt5OhV6YC+d51D gyyK2/afA9BA+geDegxxANTU/Q38IwCDKy1kbm6tLmm2RorAPkomU3PdN/hloW569hes cRiaG1QsjK1IgPNs4jzCx76iwOrXY6Iu90xXlucaVr6HPW+8MP/uvgGi0swfglWRzPV5 OcUZQSwQI++hvgDrOKk7OkYDXKdKTffE78MsXpR6TK3ixQaKOMjU96R/O8UuvDQQMDyF gKNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=rzg6hZzRBXgl051rwXKoC+kw81pJOB/AG/jzUKhZsmU=; b=PtxKRYP9WkF7MatQVz0vwC89phaSkvPJvTYI+RweltXUJllREEZtgWuvKMeU12O28W 0sUcKApKXJsbzyLHwgYbHLwTtuBaT5HWBnGRKqHPZt/kSRnXtUGFDdONJAfBQ/L06lxc KLngSfEC7y6rAjPCFHJTddg109euUtdv78Xs4/MFk6OFUmdW0UvybXETvM24vgWT390v 6eV5vSYZPad2fB/PMaNRvD5XIbWvKSzjuHow0uoYy7JXhwuzaDG6Q7ZytpVUIr98bMRa mLSphTAeBuG+Uh4CXXwSlmJyfL54h+SrHvVggh0BapjGYN/P8KrI+dJPYV1urDF/dKAo oi0A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c4si2825756ejb.183.2019.09.11.09.46.19; Wed, 11 Sep 2019 09:46:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729267AbfIKQlH (ORCPT + 99 others); Wed, 11 Sep 2019 12:41:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38798 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728794AbfIKQlH (ORCPT ); Wed, 11 Sep 2019 12:41:07 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CDF7310C0931; Wed, 11 Sep 2019 16:41:06 +0000 (UTC) Received: from localhost (ovpn-116-29.ams2.redhat.com [10.36.116.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5EC1519C6A; Wed, 11 Sep 2019 16:41:06 +0000 (UTC) From: Cornelia Huck To: Sebastian Ott , Peter Oberparleiter Cc: Heiko Carstens , Vasily Gorbik , Christian Borntraeger , linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, Cornelia Huck Subject: [PATCH] s390/cio: fix intparm documentation Date: Wed, 11 Sep 2019 18:41:03 +0200 Message-Id: <20190911164103.16156-1-cohuck@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.redhat.com [10.5.110.66]); Wed, 11 Sep 2019 16:41:06 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The common I/O layer is maintaining an "intparm" inspired by the hardware intparm for driver usage. This "intparm" is not only applicaple for ssch, but also for hsch/csch. The kerneldoc states that it is only updated for hsch/csch if no prior request is pending; however, this is not what the code does (whether that would actually desireable is a different issue.) Let's at least fix the kerneldoc for now. Fixes: b2ffd8e9a76e ("[S390] cio: Add docbook comments.") Signed-off-by: Cornelia Huck --- drivers/s390/cio/device_ops.c | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/drivers/s390/cio/device_ops.c b/drivers/s390/cio/device_ops.c index d722458c5928..65841af15748 100644 --- a/drivers/s390/cio/device_ops.c +++ b/drivers/s390/cio/device_ops.c @@ -124,9 +124,7 @@ EXPORT_SYMBOL(ccw_device_is_multipath); /** * ccw_device_clear() - terminate I/O request processing * @cdev: target ccw device - * @intparm: interruption parameter; value is only used if no I/O is - * outstanding, otherwise the intparm associated with the I/O request - * is returned + * @intparm: interruption parameter to be returned upon conclusion of csch * * ccw_device_clear() calls csch on @cdev's subchannel. * Returns: @@ -179,6 +177,9 @@ int ccw_device_clear(struct ccw_device *cdev, unsigned long intparm) * completed during the time specified by @expires. If a timeout occurs, the * channel program is terminated via xsch, hsch or csch, and the device's * interrupt handler will be called with an irb containing ERR_PTR(-%ETIMEDOUT). + * The interruption handler will echo back the @intparm specified here, unless + * another interruption parameter is specified by a subsequent invocation of + * ccw_device_halt() or ccw_device_clear(). * Returns: * %0, if the operation was successful; * -%EBUSY, if the device is busy, or status pending; @@ -256,6 +257,9 @@ int ccw_device_start_timeout_key(struct ccw_device *cdev, struct ccw1 *cpa, * Start a S/390 channel program. When the interrupt arrives, the * IRQ handler is called, either immediately, delayed (dev-end missing, * or sense required) or never (no IRQ handler registered). + * The interruption handler will echo back the @intparm specified here, unless + * another interruption parameter is specified by a subsequent invocation of + * ccw_device_halt() or ccw_device_clear(). * Returns: * %0, if the operation was successful; * -%EBUSY, if the device is busy, or status pending; @@ -287,6 +291,9 @@ int ccw_device_start_key(struct ccw_device *cdev, struct ccw1 *cpa, * Start a S/390 channel program. When the interrupt arrives, the * IRQ handler is called, either immediately, delayed (dev-end missing, * or sense required) or never (no IRQ handler registered). + * The interruption handler will echo back the @intparm specified here, unless + * another interruption parameter is specified by a subsequent invocation of + * ccw_device_halt() or ccw_device_clear(). * Returns: * %0, if the operation was successful; * -%EBUSY, if the device is busy, or status pending; @@ -322,6 +329,9 @@ int ccw_device_start(struct ccw_device *cdev, struct ccw1 *cpa, * completed during the time specified by @expires. If a timeout occurs, the * channel program is terminated via xsch, hsch or csch, and the device's * interrupt handler will be called with an irb containing ERR_PTR(-%ETIMEDOUT). + * The interruption handler will echo back the @intparm specified here, unless + * another interruption parameter is specified by a subsequent invocation of + * ccw_device_halt() or ccw_device_clear(). * Returns: * %0, if the operation was successful; * -%EBUSY, if the device is busy, or status pending; @@ -343,11 +353,12 @@ int ccw_device_start_timeout(struct ccw_device *cdev, struct ccw1 *cpa, /** * ccw_device_halt() - halt I/O request processing * @cdev: target ccw device - * @intparm: interruption parameter; value is only used if no I/O is - * outstanding, otherwise the intparm associated with the I/O request - * is returned + * @intparm: interruption parameter to be returned upon conclusion of hsch * * ccw_device_halt() calls hsch on @cdev's subchannel. + * The interruption handler will echo back the @intparm specified here, unless + * another interruption parameter is specified by a subsequent invocation of + * ccw_device_clear(). * Returns: * %0 on success, * -%ENODEV on device not operational, -- 2.20.1