From mboxrd@z Thu Jan 1 00:00:00 1970 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4EA81C433FE for ; Mon, 21 Nov 2022 12:59:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229731AbiKUM7t (ORCPT ); Mon, 21 Nov 2022 07:59:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45448 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229649AbiKUM7s (ORCPT ); Mon, 21 Nov 2022 07:59:48 -0500 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 774142936E for ; Mon, 21 Nov 2022 04:59:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1669035587; x=1700571587; h=date:from:to:cc:subject:message-id:mime-version; bh=si+DZodBVvJT8HkhhedPN4Wed1iZ0a5TOnfLApPF3VU=; b=LkBQ7p3LGNnm3kISEMw7CBHaXdpS3DwVXn5jY9zRBJQdWr9+BAJhR7iU ts2yjV7J2Nm8TazRylgKtc5vjroB0zhv/UwMJ4FGkr6RMwmRVMwqLWEpr 3Gfhi86IHEE/w7NIFZ7DvpuhQ9TiaPwJpNHDlFp2I/t5i6ULGU/BBc38N Eu0w3PvN0s+Q/E7WlEO3aEsiU5sA0P45t7da2IAiMHCE1e7ObQk5ZrgA1 RCyQI8xKdgVJ2RbUxYjuzK37e/LGOFJLt3aM8qf2gm8P4wiyRvDBiHpjW daA1gmNIVsvsQqN48dPJvZkRB6FBMgFtxea5s4N8eWh5QqiC13eQ9Ma9g Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10537"; a="340408754" X-IronPort-AV: E=Sophos;i="5.96,181,1665471600"; d="scan'208";a="340408754" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Nov 2022 04:59:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10537"; a="704551123" X-IronPort-AV: E=Sophos;i="5.96,181,1665471600"; d="scan'208";a="704551123" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 21 Nov 2022 04:59:46 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ox6Om-00FHEL-2q; Mon, 21 Nov 2022 14:59:44 +0200 Date: Mon, 21 Nov 2022 14:59:44 +0200 From: Andy Shevchenko To: devicetree@vger.kernel.org Cc: Rob Herring , Krzysztof Kozlowski Subject: Mixed types of values inside a single property Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi, Rob and Krzysztof! Today on SO one question [1] was popped up, and I, remembering a bit of the code of device properties in the Linux kernel, was a bit surprised of it in a way that reading DT specification (0.4-rc1 as of today) doesn't clarify that either. Can the specification be a bit more clear about that? Or is it me and the OP of that question who missed something in the DT spec? [1]: https://stackoverflow.com/questions/74517569/reading-tuples-in-a-devicetree -- With Best Regards, Andy Shevchenko