From patchwork Wed Sep 13 18:55:24 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Umang Jain X-Patchwork-Id: 13383692 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3296FEE0202 for ; Wed, 13 Sep 2023 18:56:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=JEWB5CBh1UTmoaaaPsDceV0CaBHb5YulnQidEct4CrM=; b=lUQm33g3EtH0RB b/H69pzX9QjFm1sH3n4H8W7LJSDcGxPqFvvjgAphXixO9OYMr/vzzneeg5ZxXGnCSxaf6T+ffP6Yh x+EKLtwHCCVuO4wL7eqoPsll8wHP25sA8ZuNjkxpX6WylnJzGNh7VQkQz5/Xckmz8uaOPhEpmOVgj ScdEjf3H1kSHoNehluglMPp2Ks/zUInx1H6HgAsfbYLiIze5059puyrT54Z0V2SrpV11u2ipOw7wy cZofsSgeGIw7j7BjQb1xadZJP5kkbLXCzFpXI/HoC8pOpb/mlTBR6e4t8rrkVRV32Bvx6+fra+mRK Ol29UZo4SZuYf4xOtVbQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qgV1j-006Zlj-0c; Wed, 13 Sep 2023 18:55:51 +0000 Received: from perceval.ideasonboard.com ([213.167.242.64]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qgV1f-006Zj9-3D; Wed, 13 Sep 2023 18:55:49 +0000 Received: from umang.jainideasonboard.com (unknown [103.86.18.170]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 7B713B1; Wed, 13 Sep 2023 20:54:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1694631249; bh=chNJdd1zcolnNrSINJke77grPOMpV8+bsyYop+wOaRo=; h=From:To:Cc:Subject:Date:From; b=HpkUBWIYpxt7jQtUdojaA1KRCB349FRTR7OA4RZpSB9d5yegO54mBmOi+9xxpykCe G75dWHjGhbbNHgjxU0ZYaDrqpubxyzh3u+88NJ5NlD+SB6BBaV/uoocmRXHh52OkqK hwmYDctllIyyvRwk4Z4EdbjdeKeEHH5bFxMjoqCA= From: Umang Jain To: linux-staging@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-rpi-kernel@lists.infradead.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Stefan Wahren , Greg Kroah-Hartman , Florian Fainelli , Adrien Thierry , Dan Carpenter , Dave Stevenson , Kieran Bingham , Laurent Pinchart , Phil Elwell , Umang Jain Subject: [RFC PATCH v2 0/4] staging: vc04: Drop custom logging Date: Thu, 14 Sep 2023 00:25:24 +0530 Message-Id: <20230913185528.770634-1-umang.jain@ideasonboard.com> X-Mailer: git-send-email 2.40.1 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230913_115548_202489_7EAA589D X-CRM114-Status: UNSURE ( 8.62 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello, This series attempts to restart the discussion on custom logging used in VC04. In the last feedback gathered in [1] it seems that the logging would rather be moved to use dynamic debug. The series tries to move in that direction. The elephant in the room is the ability of turning on/off log levels, which this series just drops. Compensated by a crude strings ("error", "warning", "info"... etc) for easier grepping. The log category are also just strings (which probably can be transformed to dynamic debug class names moving forwards?). To move forwards, I would like feedback on the broader direction. There are couple of TODOs in each of the patch (summarised in commit messages) which require case-by-case discussion. Additional high-level questions to move forwards: 1. Is loss of log levels by moving to dynamic debug, is actually a concern? Is dynamic debug a valid replacement? 2. Whether debugfs should be dropped as well, found vestigial in [2] 3. whether vchiq_log_trace() should actually be tracing support for VC04 All this is done to elimiate the TODO item in: drivers/staging/vc04_services/interface/TODO * Cleanup logging mechanism Addtional comments/questions are welcome. Thank you. Tested over media-tree master with dynamic debug configs enabled and drivers/staging/vc04_services/interface/TESTING. [1] https://lore.kernel.org/lkml/20230118115810.21979-1-umang.jain@ideasonboard.com/ [2] https://lore.kernel.org/lkml/Y8lHqd9FlxiXTLuW@kroah.com/ Umang Jain (4): staging: vc04: Convert vchiq_log_error() to use dynamic debug staging: vc04: Convert vchiq_log_warning() to use dynamic debug staging: vc04: Convert vchiq_log_info() to use dynamic debug staging: vc04: Convert vchiq_log_trace() to use dynamic debug .../interface/vchiq_arm/vchiq_arm.c | 127 +++++----- .../interface/vchiq_arm/vchiq_connected.c | 6 +- .../interface/vchiq_arm/vchiq_core.c | 225 ++++++++---------- .../interface/vchiq_arm/vchiq_core.h | 46 ++-- .../interface/vchiq_arm/vchiq_dev.c | 41 ++-- 5 files changed, 232 insertions(+), 213 deletions(-) base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d