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 01198C433EF for ; Wed, 4 May 2022 18:38:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377081AbiEDSlp (ORCPT ); Wed, 4 May 2022 14:41:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34388 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1377102AbiEDSiX (ORCPT ); Wed, 4 May 2022 14:38:23 -0400 Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 44CD5201BB for ; Wed, 4 May 2022 11:28:41 -0700 (PDT) Received: by mail-ot1-x32d.google.com with SMTP id 88-20020a9d0ee1000000b005d0ae4e126fso1442913otj.5 for ; Wed, 04 May 2022 11:28:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=TQPIA3VoumXyz1RrJSRcgA9lX+Pt6VG1KcKf5rCLbxQ=; b=y1IysrpGVOmONLnNwZEc588WNAHRPAVbFpbSh/tJ4Au9pwjAy+vAt6bt+DJFv/wPCj y9n5yzmHwrbKGHGMfUf7W/KJd+IFmpwCMHVhCkYNtZo3mdz1V/opKepzQdrFWSaUWUlt Q70UsdaJdM4/hzlkecq9pUbmdwSoE3i7m7s9GewikuTR9bPIqoPmZXHhpPr+gC72pR/p Z29aM2mn1GTHHp5RBCcB8Wzf5wtwdcen1Du1C6BZYvk2ehSnXJPFYMcW3fAiLbQqiG2a 0seyeIzRe4cMUdCb2YpX/yt9KfODo/fC4RvdEplUg9NtsQHmYnhP3ofpAuk4FEYS1i7w YVBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=TQPIA3VoumXyz1RrJSRcgA9lX+Pt6VG1KcKf5rCLbxQ=; b=iP5Q3Vj3rl4woi1XDCvWIz/ZZ9JGGlQfYb/+WgcX2lH71Vq9f1z6W9FEqIbLcolsi8 1t8z9qhYy77PT8hlT7kkVeNvuaPelgftaQBAPfyhz3YQeR/znHTpQ9QhLlAV3sdUAd3e t8RLAH1w2e32k41RNWPVGlrylsEZDlAa/wxrhkUl2XUG6X6CmnDErcl38XL9qa74YcoB 1u+ZqMnkOg6Kr1ecxG8v025B7Knf6345y/7Y+R7ofV1rkjlOvPLB7xgBLFJFUJq0uy1X QBV4hbkaSNEwJL2DQEdE0pbBSn2D5Z57bcLLfBBNhhvIkyus/WIbp53p9m0DO2WNPECT lMWw== X-Gm-Message-State: AOAM530S4zHaXwgkW1h1PKsw74Db/csYuIAI97PNG9hGEiYAbBAK+Sny 9eT01cmK8NrO+5WgKeH+FTXFDA== X-Google-Smtp-Source: ABdhPJxYkiegcJ9IRk6D1ytXYH8Rm5Z9s0sDkK09+L3SZz4yCj9MynlTPJUgbX3gQGvlpBMyFfR0+A== X-Received: by 2002:a9d:2621:0:b0:606:254a:bc78 with SMTP id a30-20020a9d2621000000b00606254abc78mr4469271otb.57.1651688920275; Wed, 04 May 2022 11:28:40 -0700 (PDT) Received: from ripper (104-57-184-186.lightspeed.austtx.sbcglobal.net. [104.57.184.186]) by smtp.gmail.com with ESMTPSA id y14-20020a0568302a0e00b006060322123fsm3783845otu.15.2022.05.04.11.28.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 May 2022 11:28:39 -0700 (PDT) Date: Wed, 4 May 2022 11:30:25 -0700 From: Bjorn Andersson To: Doug Anderson Cc: Sai Prakash Ranjan , matvore@chromium.org, Andy Gross , "Reviewed-by : Stephen Boyd" , LKML , linux-arm-msm Subject: Re: (subset) [PATCH] soc: qcom: socinfo: Add another ID for sc7180 Message-ID: References: <20220502173338.1.I26eca1856f99e6160d30de6d50ecab60e6226354@changeid> <165168485227.3730817.11549721304895378126.b4-ty@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Wed 04 May 10:51 PDT 2022, Doug Anderson wrote: > Hi, > > On Wed, May 4, 2022 at 10:21 AM Bjorn Andersson > wrote: > > > > On Mon, 2 May 2022 17:33:45 -0700, Douglas Anderson wrote: > > > It appears the some sc7180 devices, like the one in my > > > sc7180-trogdor-homestar, report an ID of 407 instead of 425. Add > > > another ID into the list. > > > > > > > > > > Applied, thanks! > > > > [1/1] soc: qcom: socinfo: Add another ID for sc7180 > > commit: c35886d605604e0b03cdd835ae3249dc1fe0cc2a > > Hmm. Did you see the responses from Sai [1] about this? He seemed to > indicate that there might be some issue here because he thought 407 > was supposed to be a different SoC. Are we sure we want to land this > patch while we're sorting it out? > I stared at the thread but didn't see his reply for some reason. Congrats on the getting the random SoC in your device ;) As this was the top patch on drivers-for-5.19, I just popped that off and pushed the branch again. Let me know when you've figured the numbering out (and if it turns out to be the mobile id I wouldn't mind carrying that in the table) Regards, Bjorn > [1] https://lore.kernel.org/r/13819b2d-26f0-14f4-9cb9-affb6b18f13d@quicinc.com/