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 6BD16EE49B0 for ; Fri, 25 Aug 2023 06:39:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242090AbjHYGjM (ORCPT ); Fri, 25 Aug 2023 02:39:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242256AbjHYGiu (ORCPT ); Fri, 25 Aug 2023 02:38:50 -0400 Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F09661FEF for ; Thu, 24 Aug 2023 23:38:45 -0700 (PDT) Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-52a3ff5f0abso868059a12.1 for ; Thu, 24 Aug 2023 23:38:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fairphone.com; s=fair; t=1692945524; x=1693550324; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-transfer-encoding:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1SSRgsqWGE/RACDHj1qc7eoiU1kp65t711DUZ8q0Mxk=; b=EoSOllFIEBw85fBVae2XuxA9YZCxndm5zMLl/wqeYioP+1+19xOWCLJglOyz+w/krA I27be0wi+BoWh19f/mogs6yGFshx3OjRm5z2LUxDpPtPwjpSuzj1iLmkv+ijhZ1sFCUO UnctSiLmJvpTW4DA1/PjLLNff7aKd19zpVFH2jE5xvPKiQ1a1uMfRp/7dKTesao2zhk/ jHCnKbia4wPcJXTK92FPZNK0W7EQ29bvWzAIW3d4E6VoewulfEjU9Igasu6Hx73UJhM7 xecUcuxlAiquFMhKwVlO1DGOzrbIOrC3v1B1mMIEelGwRYnglxTxdFwxT6OkAMkfe/mp d2Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692945524; x=1693550324; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=1SSRgsqWGE/RACDHj1qc7eoiU1kp65t711DUZ8q0Mxk=; b=P1exC4ddzkNiiPw9VSHVSsK5s/zo5/WhiJ6UYnCnfa3xR+QSRaCbOam8tcDldHKpti EgkgooAUu4Cy2653Ml3tt+CX19Hhre402gMS1KwlAv2j5sERnv4U2LL7F8HPT4UA3Hq0 +J2Y32ipHzKC3gfjKkfcqLZNzvi0oJ0JNJxyN7MzhXEku4k5o2O7L67pGRgTQyrise/h /64avCp7lWSRBkaC30NXAafrCny3xyLhHqZf0TGQhCamJ/fO+Odt9yxjq2VjMbEPeLsK 7Ho4iuSikJtloyladmuvB5o0aflsUvKB17gVkDKhYbhuABbRG8hOwZDAF+avhiBRdCtl Mbbg== X-Gm-Message-State: AOJu0Yzthqbc2v6/SxbA4DWH8GxU25jyvlisU7/imi/CDpfZzhZgaa71 fzIqxA0mVtPt5DnPUUvx8Q44xw== X-Google-Smtp-Source: AGHT+IGIN+a9Tsuplje7An/26N8i6OFoKx8k6Zzw0oy9lXO91uIOWqYbG5+7wH8oDVAfS7RB4mk50Q== X-Received: by 2002:a17:907:78d8:b0:9a1:e941:6f48 with SMTP id kv24-20020a17090778d800b009a1e9416f48mr4943404ejc.13.1692945524404; Thu, 24 Aug 2023 23:38:44 -0700 (PDT) Received: from localhost (144-178-202-138.static.ef-service.nl. [144.178.202.138]) by smtp.gmail.com with ESMTPSA id x18-20020a170906805200b0097073f1ed84sm603963ejw.4.2023.08.24.23.38.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 24 Aug 2023 23:38:44 -0700 (PDT) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 25 Aug 2023 08:38:43 +0200 Message-Id: Cc: "Andy Gross" , "Bjorn Andersson" , "Konrad Dybcio" , "Alim Akhtar" , "Avri Altman" , "Bart Van Assche" , "Krzysztof Kozlowski" , "Iskren Chernev" , "Manivannan Sadhasivam" , "Conor Dooley" , "Herbert Xu" , "David S. Miller" , "Martin K. Petersen" , , , , , <~postmarketos/upstreaming@lists.sr.ht>, , , "Krzysztof Kozlowski" , "Bhupesh Sharma" , "Eric Biggers" Subject: Re: [PATCH v6 0/4] Fix some issues in QCOM UFS bindings From: "Luca Weiss" To: "Rob Herring" X-Mailer: aerc 0.15.2 References: <20230814-dt-binding-ufs-v6-0-fd94845adeda@fairphone.com> <20230824171052.GA1037612-robh@kernel.org> In-Reply-To: <20230824171052.GA1037612-robh@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu Aug 24, 2023 at 7:10 PM CEST, Rob Herring wrote: > On Mon, Aug 14, 2023 at 12:14:12PM +0200, Luca Weiss wrote: > > This series aims to solve the dtbs_check errors from the qcom ufs > > bindings. It has changed in scope a bit since v1, so it may be a bit al= l > > over the place. > >=20 > > Signed-off-by: Luca Weiss > > --- > > Changes in v6: > > - Rebase on linux-next > > - Drop applied dts patch > > - Pick up tags > > - Link to v5: https://lore.kernel.org/r/20221209-dt-binding-ufs-v5-0-c9= a58c0a53f5@fairphone.com > >=20 > > Changes in v5: > > - Convert sm8450.dtsi to use qcom,ice property, so stop modifying schem= a > > for sm8450 and only add qcom,ice property. > > - Move reg-names names to top-level with only minItems/maxItems in the > > 'if' > > - Link to v4: https://lore.kernel.org/r/20221209-dt-binding-ufs-v4-0-14= ced60f3d1b@fairphone.com > >=20 > > Changes in v4: > > - Pick up tags > > - Rebase on linux-next (again) > > - Link to v3: https://lore.kernel.org/r/20221209-dt-binding-ufs-v3-0-49= 9dff23a03c@fairphone.com > >=20 > > Changes in v3: > > - Drop applied patch > > - Pick up sm6115 patch from v5 https://lore.kernel.org/all/202210300942= 58.486428-2-iskren.chernev@gmail.com/ > > - Rebase on linux-next > > - Link to v2: https://lore.kernel.org/r/20221209-dt-binding-ufs-v2-0-dc= 7a04699579@fairphone.com > >=20 > > Changes in v2: > > - Add new patch adding reg-names to sm6115 & rebase series on top of sm= 6115 > > addition > > - Fix binding example after sm8450 move, split this patch from original= patch > > since it became too big > > - Move reg-names definition to top-level > > - Link to v1: https://lore.kernel.org/r/20221209-dt-binding-ufs-v1-0-8d= 502f0e18d5@fairphone.com > >=20 > > --- > > Iskren Chernev (1): > > dt-bindings: ufs: qcom: Add sm6115 binding > >=20 > > Luca Weiss (3): > > dt-bindings: ufs: qcom: Add reg-names property for ICE > > dt-bindings: ufs: qcom: Add ICE to sm8450 example > > dt-bindings: crypto: ice: Document sm8450 inline crypto engine > >=20 > > .../bindings/crypto/qcom,inline-crypto-engine.yaml | 1 + > > .../devicetree/bindings/ufs/qcom,ufs.yaml | 44 ++++++++++++++= ++++++++ > > 2 files changed, 45 insertions(+) > > I guess the subsystem maintainers aren't going to pick this up, so I've= =20 > applied it. Thanks Rob, appreciate it! > > Rob