From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 20AA13769E5; Mon, 29 Jun 2026 14:09:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.9 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782742163; cv=none; b=EaqjLjCU9cpNyzMm6y2avpzhvP7c53rUg9AupzyFkVCT4VbcbM2sk09hTL7xw5PZj6orWuIRRH7t55HKMUsnWYTjdSADQMF4RZtGu1dubeASpDT3QjyfEZEgiqjC769N3r7iLTTYj51WryUkSfJMVaQ1F+HLw3LlGvzHO46MqvE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782742163; c=relaxed/simple; bh=teeX39/m1S4D7PMAq39faNk4sI6sySbT2nT+YJyHiQI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=UQdkxNwg/XAOOnswhPlfvsVH9chFS1osoXJa0oiNV4XXEr2DANS7aobEx4v41EqUYojBvoRynHDLxcilktkUT9w5xfQAOYjWZH0oyGnE5Lm8E7DxzVDWqB52I7SBbjNSfZQol/mM1pVLarKsNzCmoGuaP4Q+hGdhpUp0syGHgrs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=PyXHNHw+; arc=none smtp.client-ip=192.198.163.9 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="PyXHNHw+" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1782742162; x=1814278162; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=teeX39/m1S4D7PMAq39faNk4sI6sySbT2nT+YJyHiQI=; b=PyXHNHw+TJ9cueQvYTkfOEmfPV+2cb9WM2BAyKOQMzP9obCRf7ZGthDH UxAMeuEpWP0lfG8tNqUa6r5VfCuVFKsUupnw3KhYjWt9kZ6hk+E9vafLj ZpYXUQOs/Qo8nk2AKQFMLYZ2cihriqHbHIfHu053SXFad27CpLC/qQz30 4xYW30gTd9r0dtyOLYdoGUU6HgmweB3hLcSJN8zjAucHG4gobty5RXqUB +Xv5eVldEr25WtJpgSLYqcVyQaMqW0GPQobgrnTk3W5a5an6tZf56UA5N URWBbxJjNqlIj90MG6yT9MQjv9UokDVRNvH/brouKM5zZmcl7kwohoHCO A==; X-CSE-ConnectionGUID: jfEIin4XQTW+/J/255776g== X-CSE-MsgGUID: sl5OO3+hS/y9seXsr36Aug== X-IronPort-AV: E=McAfee;i="6800,10657,11831"; a="94088230" X-IronPort-AV: E=Sophos;i="6.24,232,1774335600"; d="scan'208";a="94088230" Received: from fmviesa006.fm.intel.com ([10.60.135.146]) by fmvoesa103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2026 07:09:21 -0700 X-CSE-ConnectionGUID: hNYDjxHyQqqxBfhoCt1Z+g== X-CSE-MsgGUID: h7anExFSRryvVsfY/Rlw5w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.24,232,1774335600"; d="scan'208";a="247514569" Received: from kniemiec-mobl1.ger.corp.intel.com (HELO localhost) ([10.245.244.207]) by fmviesa006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2026 07:09:17 -0700 Date: Mon, 29 Jun 2026 17:09:14 +0300 From: Andy Shevchenko To: Jinseob Kim Cc: Jonathan Cameron , Rob Herring , Krzysztof Kozlowski , Conor Dooley , David Lechner , Nuno =?iso-8859-1?Q?S=E1?= , Andy Shevchenko , Jonathan Corbet , Shuah Khan , linux-iio@vger.kernel.org, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC v6 0/5] iio: add Open Sensor Fusion IIO driver Message-ID: References: <20260628191337.937-1-kimjinseob88@gmail.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260628191337.937-1-kimjinseob88@gmail.com> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Mon, Jun 29, 2026 at 04:13:32AM +0900, Jinseob Kim wrote: > Open Sensor Fusion (OSF) devices expose a UART/serdev host interface > for a sensor aggregation hub. This RFC adds a Linux IIO driver that > parses OSF frames and creates IIO devices at runtime from capability > reports provided by the device firmware. > > When the corresponding capabilities are reported, the driver exposes > accelerometer, gyroscope, magnetometer, and temperature data as IIO > devices named osf-accel, osf-gyro, osf-magn, and osf-temp. > > This remains RFC while the binding, protocol subset, runtime discovery > model, and driver-facing ABI are reviewed. Where are the lore links to the previous versions? -- With Best Regards, Andy Shevchenko