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 95451C433EF for ; Mon, 11 Apr 2022 06:42:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245031AbiDKGpC (ORCPT ); Mon, 11 Apr 2022 02:45:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245028AbiDKGpA (ORCPT ); Mon, 11 Apr 2022 02:45:00 -0400 Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C19D8289A0 for ; Sun, 10 Apr 2022 23:42:45 -0700 (PDT) Received: by mail-ej1-x62e.google.com with SMTP id bv19so5738047ejb.6 for ; Sun, 10 Apr 2022 23:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=oeGY+i1594VzqaZYPeCwfNtowmuuBm84SvUo17g7pww=; b=UxJIcbi+k0bsNmAhFdx5LRRsGrLtn1cxDTlmkQ6rEecQxLd3ZlQzxbbXpBXlqGMqW2 mcunz3PDYykTTMlJMvdGv4Pf0VZ+tO4dhzuj3cMkad/CJAfyQhY44MenyyiMs4zO9B4i GgLx+x1mfFRfOJwLXHFGacQUj38rWDNNamcoR+5tizxZXj1+kbnd3Qmg0bDStwp2AELF QqXJYc0ZMuaOkHcF+9nCkY+rzYgeOnqB7VcYdHcQu8MS2yal6THrzsFfHG3elJfIqqwH 8iYXRWblSPgVH+ym5mLkJORVDKtpdrp6EtblUZ8AZZJcoxXKvneyiS38Xhy4kI7VZY80 ABHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=oeGY+i1594VzqaZYPeCwfNtowmuuBm84SvUo17g7pww=; b=whqYAm8zAGVBfm8+NM94tjenjAO7QCc4h9tgxu/3lnVFylpB7GZAL9Xpqt/vAwb3q+ //ae5e7cydMbKERw6tNdREvmdW1I7SSv0OrCV1ctAstjpSGsFPI8dCxzOs7z3dJcjkru qchpr9dn9xWkvJXLz1mJU9VeHJ368wlWTkDPLVJUJcGHhy5yRSgyL93m2MK4cov0l9we SFv4cT0gfvQOpld/bGXqf59RkKRk1oNBla2OzOhZyo+sNiw1Dkp62YSkjVmJAm8kboy0 FuLk8DKeaUuf/G8BlA6V/Y5ROeZ4cG0Wp0w2jHb6yco5iBbZA1hKJyL9/L98yCjOLk9w Kryg== X-Gm-Message-State: AOAM532O/fKE6nH8V3aJtVH2Klp02adM1IiMkM9z1eAhjgnnMOslV9fF 8zmQi/HzpiHN7zq32FBJCeJsyg== X-Google-Smtp-Source: ABdhPJxWQegr0c/5XL0ZzwCad1TzFMKBUFGyQOBP0ER/rivBmSCr6Xyxq34fdHrUvtNT/lD5OtP94w== X-Received: by 2002:a17:907:9705:b0:6e4:b769:286f with SMTP id jg5-20020a170907970500b006e4b769286fmr27845750ejc.728.1649659364246; Sun, 10 Apr 2022 23:42:44 -0700 (PDT) Received: from [192.168.0.191] (xdsl-188-155-201-27.adslplus.ch. [188.155.201.27]) by smtp.gmail.com with ESMTPSA id r29-20020a50c01d000000b00415fb0dc793sm14810681edb.47.2022.04.10.23.42.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 10 Apr 2022 23:42:43 -0700 (PDT) Message-ID: <6c4b6eac-86d8-eb93-37a5-d0fa9bf2a7d2@linaro.org> Date: Mon, 11 Apr 2022 08:42:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH V4 1/3] dt-bindings: mmc: imx-esdhc: Update compatible fallbacks Content-Language: en-US To: Adam Ford , linux-mmc@vger.kernel.org Cc: aford@beaconembedded.com, haibo.chen@nxp.com, Ulf Hansson , Rob Herring , Krzysztof Kozlowski , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20220410193544.1745684-1-aford173@gmail.com> From: Krzysztof Kozlowski In-Reply-To: <20220410193544.1745684-1-aford173@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org On 10/04/2022 21:35, Adam Ford wrote: > The SDHC controller in the imx8mn and imx8mp have the same controller > as the imx8mm which is slightly different than that of the imx7d. > > Using the fallback of the imx8mm enables the controllers to support > HS400-ES which is not available on the imx7d. After discussion with NXP, > it turns out that the imx8qm should fall back to the imx8qxp, because > those have some additional flags not present in the imx8mm. > > Mark the current state of the fallbacks as deprecated, and add the > proper fallbacks so in the future, the deprecated combination can be > removed and prevent any future devices from using the wrong fallback. > > Suggested-by: haibo.chen@nxp.com > Signed-off-by: Adam Ford Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof