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 A43D4ECAAD8 for ; Wed, 31 Aug 2022 06:23:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229843AbiHaGX0 (ORCPT ); Wed, 31 Aug 2022 02:23:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38282 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229646AbiHaGXZ (ORCPT ); Wed, 31 Aug 2022 02:23:25 -0400 Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4CAECBD108 for ; Tue, 30 Aug 2022 23:23:24 -0700 (PDT) Received: by mail-lf1-x12c.google.com with SMTP id p16so522172lfd.6 for ; Tue, 30 Aug 2022 23:23:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=sG8qQX99gFK4yoHoKn1Te6zMXWrXBOfDL+SjtxXraow=; b=VLeRXkSI9xzluqbrtoexL6/woaBxAqAt86KOLzWX2tiaEbNAu7jebpt79pR+gAyIXH rMrki1qaEQxEQVFIUqx2laUPLlU+yiqsrj3/9YIctsuKMt+oWIV3ruqkYazPSmqr3YFN gfCjS/3wSyIOu2gTKsqF684/JK1PEu4XNmM7QiyQt1qqgEBHdRQu8hgqAI6MgXcGaToq STmaE2cO2BVkejVzfGqJIc9NVfIdyKCtJnoBcTNwbo7ZhqvzB36T3rCS+CFQndf82Iz7 4I9BnepR+SKDA1MaUkQiqzNfDIw+IzX+AitTllmE32OWBWEr0VoUfH2SrB7Xs0G7S5Qv W4KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=sG8qQX99gFK4yoHoKn1Te6zMXWrXBOfDL+SjtxXraow=; b=Ktu1JKqHDTZToAnTVacjNP8A6G55wL5jA09Wwofeu4QgqaCwbmBuuhKMyIbkK39O/p YDU0rbkPTeA6m4wTDBjgAJS3sVY4DeR896ItEvb2M6DGuvVeHSt+diWCc4Wx4Q+NKQvL uemHVuReI99v7sUYn1NZWxhUCFWLyve+zGT4kUR09dstujvEZGIoULdspOYMDs+Ve3LU kiuGYiTadIiLvVzMEWC/5gnvBgcz4E2i5Bzg1hW534o9pQ4DwdWs124X+4GX9AB+USoR +p8KennVZLONUGhsd/NTP/hjkNv4I0UOoL2NCIHSMorMpedDLzOtCNkxgXbnUttO1V7g zsnA== X-Gm-Message-State: ACgBeo2lIPvUSQDqYPheEslkvwnhEp2YidQztXujLLh2KKiGKn4kpc0+ VKOJyl5TIodzQrabvUWh7Af4tQ== X-Google-Smtp-Source: AA6agR5BmtOnQlEfLdxdo+dKqIZi/cCEsfH7kp1nabWPpiU2DtSDu1l5/8vzYaNFyjpJVl4vA8Nx+g== X-Received: by 2002:a19:e00d:0:b0:492:e5a5:588b with SMTP id x13-20020a19e00d000000b00492e5a5588bmr8309119lfg.243.1661927002695; Tue, 30 Aug 2022 23:23:22 -0700 (PDT) Received: from [192.168.28.124] (balticom-73-99-134.balticom.lv. [109.73.99.134]) by smtp.gmail.com with ESMTPSA id f13-20020a056512092d00b00492ed031aacsm1868997lft.173.2022.08.30.23.23.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 Aug 2022 23:23:21 -0700 (PDT) Message-ID: Date: Wed, 31 Aug 2022 09:23:21 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [PATCH 2/4] dt-bindings: memory: Add numeric LPDDR compatible string variant Content-Language: en-US To: Julius Werner Cc: Rob Herring , Dmitry Osipenko , Doug Anderson , Jian-Jia Su , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220831013359.1807905-1-jwerner@chromium.org> <20220831013359.1807905-3-jwerner@chromium.org> From: Krzysztof Kozlowski In-Reply-To: <20220831013359.1807905-3-jwerner@chromium.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 31/08/2022 04:33, Julius Werner wrote: > This patch allows a new kind of compatible string for LPDDR parts in the > device tree bindings, in addition to the existing hardcoded > , strings. The new format contains manufacturer and > part (revision) information in numerical form, such as lpddr3-ff,0201 > for an LPDDR3 part with manufacturer ID ff and revision ID 0201. This > helps cases where LPDDR parts are probed at runtime by boot firmware and > cannot be matched to hardcoded part numbers. Please describe your case here as example. Best regards, Krzysztof