From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 26134225A8; Fri, 29 Mar 2024 18:51:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=13.77.154.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711738286; cv=none; b=UAlb+3EXqVNo6T6D8sRiILvBAGrMUWclut0sx3HXq5xEjcC4EebwPlOvFT8XaLPYXERk4Gc2lIcNKBqGSRuiJbUEbRRBFEOr6GsYGVHKaJMkC4aXe02APKrxfvCvLN4xo+m8LoZm6naPWDVOT1FlWXxl0D1KtOvDTyLuA+C8cos= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711738286; c=relaxed/simple; bh=Ys+kBNBHijzDi2YWXzThWwp5KAH+FSeQOJSrMGqWnb0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=p2xo8iMtj5HnHCWnpW+bi1CfAIrq4TzNnxD8dSVG24rNIw6touU/R6DhpGysdaPNbHvSxoBgNyBIyyI6gSk/aNL4OxgLPwCwn5jtKD7fNwccTsYEZt2Gspz6oa9RGBXajeQDGqItxh7Nu5LRrUSufuumYg/ybmuv1HCqTHQxojg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com; spf=pass smtp.mailfrom=linux.microsoft.com; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b=pXGtnHj3; arc=none smtp.client-ip=13.77.154.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.microsoft.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b="pXGtnHj3" Received: from [100.64.128.229] (unknown [20.29.225.195]) by linux.microsoft.com (Postfix) with ESMTPSA id 3DC7F20E6F42; Fri, 29 Mar 2024 11:51:22 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 3DC7F20E6F42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1711738284; bh=/pwtgF4mJa43U7u8eGPihHXysR53d8MYCc7SQXhSzb8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=pXGtnHj3DxKqLXh0cvZCSvcaLvUsOJN/dP3lwRNbukpYU9EaB53wcWvXKvtfs1jy5 bJOw7CGRycUoouJw+APpXY6nb+neaFD76BLiDLQVXc02pqRxYlxecAeIpSrNcIxic/ vz7SB5uqZmwS7X85Y0Jv1eOtFAQjodiyD0paH60Y= Message-ID: Date: Fri, 29 Mar 2024 11:51:21 -0700 Precedence: bulk X-Mailing-List: linux-fbdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v0 02/14] drm/amdgpu,drm/radeon: Make I2C terminology more inclusive To: Andi Shyti Cc: Alex Deucher , =?UTF-8?Q?Christian_K=C3=B6nig?= , "Pan, Xinhui" , David Airlie , Daniel Vetter , Harry Wentland , Leo Li , Rodrigo Siqueira , Evan Quan , Hawking Zhang , Candice Li , Ran Sun , Alexander Richards , AngeloGioacchino Del Regno , Neil Armstrong , Heiner Kallweit , Hamza Mahfooz , Ruan Jinjie , Alan Liu , Aurabindo Pillai , Wayne Lin , Samson Tam , Alvin Lee , Charlene Liu , Sohaib Nadeem , Lewis Huang , Tom Chung , Bhawanpreet Lakha , Meenakshikumar Somasundaram , George Shen , Aric Cyr , Jun Lei , Nicholas Kazlauskas , Qingqing Zhuo , Dillon Varone , Le Ma , Lijo Lazar , Asad kamal , Kenneth Feng , Ma Jun , Mario Limonciello , Yang Wang , Darren Powell , Yifan Zhang , "open list:RADEON and AMDGPU DRM DRIVERS" , "open list:DRM DRIVERS" , open list , Wolfram Sang , "open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS" , "open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS" , "open list:DRM DRIVER FOR NVIDIA GEFORCE/QUADRO GPUS" , "open list:I2C SUBSYSTEM HOST DRIVERS" , "open list:BTTV VIDEO4LINUX DRIVER" , "open list:FRAMEBUFFER LAYER" , Andi Shyti References: <20240329170038.3863998-1-eahariha@linux.microsoft.com> <20240329170038.3863998-3-eahariha@linux.microsoft.com> Content-Language: en-CA From: Easwar Hariharan In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 3/29/2024 10:38 AM, Andi Shyti wrote: > Hi, > > >>>> with more appropriate terms. Inspired by and following on to Wolfram's >>>> series to fix drivers/i2c/[1], fix the terminology for users of >>>> I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists >>>> in the specification. >>> >>> The specification talks about: >>> >>> - master -> controller >>> - slave -> target (and not client) >>> >>> But both you and Wolfram have used client. I'd like to reach >>> some more consistency here. >> >> I had the impression that remote targets (i.e external to the device) were to be called clients, >> e.g. the QSFP FRUs in drivers/infiniband, and internal ones targets. >> I chose the terminology according to that understanding, but now I can't find where I got that >> information. > > The word "client" does not even appear in the documentation (only > one instance in the i3c document), so that the change is not > related to the document as stated in the commit log. Unless, of > course, I am missing something. > > I'm OK with choosing a "customized" naming, but we need to reach > an agreement. > > I raised the same question to Wolfram. > > Thanks, > Andi I don't have a preference between using target and client. As I mentioned in the thread fork, my information came entirely from Wolfram's cover letter and patch messages. I'll follow along with whatever you and Wolfram settle on. Thanks, Easwar