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 6015FC4332F for ; Tue, 13 Dec 2022 14:37:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235951AbiLMOhX (ORCPT ); Tue, 13 Dec 2022 09:37:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229786AbiLMOhT (ORCPT ); Tue, 13 Dec 2022 09:37:19 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CBE4821269 for ; Tue, 13 Dec 2022 06:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670942185; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=YeA7rNz9YtNXa30NSFNa5/BE9ikSCHuGqIiQHRpjT3Q=; b=XoZhwFEhfIlyDaNVvorvRncIsGCxsgoCnax4fRxpGxFcCDXjZVaD/1IajgtRwAmkeBBt9+ HqAp3GcSs5P9cTQg/dZl79ErziplesEPuTUN6lsRECKkx79evCQUO+a/nTudxfwttKt2XN 1L0+0Nf1lltjbZl7sgK7lNS4yBrhmuE= Received: from mail-il1-f197.google.com (mail-il1-f197.google.com [209.85.166.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-599-o7pu4dDPNkqtLyAUoWGeaQ-1; Tue, 13 Dec 2022 09:36:23 -0500 X-MC-Unique: o7pu4dDPNkqtLyAUoWGeaQ-1 Received: by mail-il1-f197.google.com with SMTP id j11-20020a056e02218b00b00304b148969dso5330627ila.13 for ; Tue, 13 Dec 2022 06:36:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=YeA7rNz9YtNXa30NSFNa5/BE9ikSCHuGqIiQHRpjT3Q=; b=SOEaxbIfddpl9TBkKep7/Jwko+mojCfWY7Xlmn+AwXoc4z4CneyOoxJ8BHycoRf9y/ sygIMn6BKEBoSV0H591st7CY/l1OSs8ZUcr3hjUzR75luCJw1Cm1SmI7uex7TDZ0w8GQ yR/9eO541sFa+QUeOgDDv16pIxLcckx8Hn41DgH+e/wGG3puiB8+UP+43iPjEJ90piJs Z+ZuFxQOAqcJu+n3JVTZ8Ff45QcP84X/NS69/aYzSbNUN8wTdg2L4WVvW95YVJDZEdMs IOa7f7o124vnex/dwkKejArwRiWw3wTV0pckFWWmaT62p40DdAmlRA66B7F3VSshKDgF sCfA== X-Gm-Message-State: ANoB5pmhL4tNw7NDTzJ220nt6Yswf3c862mmCfJfNS13PGGhpmhY4gSi UJZ7MwtCBydHYLUTzCwTr+K64RU45BP2ahIpx+n9fb3b4353gnpTzn7PI5cjQ1b4k3NcWsSNX5H AZaxInkyntZfYIFiWDDGpTqod X-Received: by 2002:a5e:d903:0:b0:6de:d90e:ee05 with SMTP id n3-20020a5ed903000000b006ded90eee05mr10135414iop.2.1670942182512; Tue, 13 Dec 2022 06:36:22 -0800 (PST) X-Google-Smtp-Source: AA0mqf5mLwxzWPfSBfxmcsXPVziNTpTyuENiy9aAV9FJntRMZ3j2oQKc8i8SHP3epsMHh0EojGMExA== X-Received: by 2002:a5e:d903:0:b0:6de:d90e:ee05 with SMTP id n3-20020a5ed903000000b006ded90eee05mr10135404iop.2.1670942182262; Tue, 13 Dec 2022 06:36:22 -0800 (PST) Received: from x1 (c-73-214-169-22.hsd1.pa.comcast.net. [73.214.169.22]) by smtp.gmail.com with ESMTPSA id y18-20020a027312000000b003760a908bfasm875133jab.169.2022.12.13.06.36.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 13 Dec 2022 06:36:21 -0800 (PST) Date: Tue, 13 Dec 2022 09:36:19 -0500 From: Brian Masney To: Javier Martinez Canillas , Shazad Hussain Cc: Krzysztof Kozlowski , Mark Brown , andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@linaro.org, robh+dt@kernel.org, johan+linaro@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, ahalaney@redhat.com, echanude@redhat.com, linux-spi@vger.kernel.org Subject: Re: [PATCH 4/4] arm64: dts: qcom: sc8280xp: add missing spi nodes Message-ID: References: <20221212182314.1902632-1-bmasney@redhat.com> <20221212182314.1902632-5-bmasney@redhat.com> <77c29d8c-34b3-f508-26bf-22520ccc1f2a@linaro.org> <13238048-f07c-3e8d-f170-5330ce94767c@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13238048-f07c-3e8d-f170-5330ce94767c@redhat.com> User-Agent: Mutt/2.2.7 (2022-08-07) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 13, 2022 at 02:08:47PM +0100, Javier Martinez Canillas wrote: > On 12/13/22 14:02, Krzysztof Kozlowski wrote: > > On 13/12/2022 13:27, Brian Masney wrote: > > qcom,spi-video-codec is still not specific enough. You need to describe > > real device behind spidev. To be clear - you do not describe userspace, > > but the device. > > > > Agree. > > I believe Brian just used "qcom,spi-video-codec" as an example but is only > a make up name to illustrate the concept. QC needs to determine what would > be the correct tuple for the IP block that the user-space > driver will drive. Yes, that was just an example. Shazad: Is this thread clear about what QC needs for spidev? I'll let QC take care of sending patch(es) to add the various compatibles since I'm not sure what hardware will be backed by spidev. I'll take care of making sure that sc8280xp.dtsi gets the spi controller nodes added. Brian