mbox series

[v7,0/3] Add dedicated Qcom ICE driver

Message ID 20230408214041.533749-1-abel.vesa@linaro.org
Headers show
Series Add dedicated Qcom ICE driver | expand

Message

Abel Vesa April 8, 2023, 9:40 p.m. UTC
As both SDCC and UFS drivers use the ICE with duplicated implementation,
while none of the currently supported platforms make use concomitantly
of the same ICE IP block instance, the new SM8550 allows both UFS and
SDCC to do so. In order to support such scenario, there is a need for
a unified implementation and a devicetree node to be shared between
both types of storage devices. So lets drop the duplicate implementation
of the ICE from both SDCC and UFS and make it a dedicated (soc) driver.

The v6 is here:
https://lore.kernel.org/all/20230407105029.2274111-1-abel.vesa@linaro.org/

Changes since v6:
 * Dropped the patches 1, 3 and 6 as they are already in Bjorn's tree.
 * Dropped the minItems for both the qcom,ice and the reg in the
   qcom,ice compatile subschema, in the ufs schema file,
   like Krzysztof suggested

Changes since v5:
 * See each individual patch for changelogs.

Changes since v4:
 * dropped the SDHCI dt-bindings patch as it will be added along
   with the first use of qcom,ice property from an SDHCI DT node


Abel Vesa (3):
  dt-bindings: ufs: qcom: Add ICE phandle
  scsi: ufs: ufs-qcom: Switch to the new ICE API
  mmc: sdhci-msm: Switch to the new ICE API

 .../devicetree/bindings/ufs/qcom,ufs.yaml     |  24 ++
 drivers/mmc/host/Kconfig                      |   2 +-
 drivers/mmc/host/sdhci-msm.c                  | 223 ++++------------
 drivers/ufs/host/Kconfig                      |   2 +-
 drivers/ufs/host/Makefile                     |   4 +-
 drivers/ufs/host/ufs-qcom-ice.c               | 244 ------------------
 drivers/ufs/host/ufs-qcom.c                   |  99 ++++++-
 drivers/ufs/host/ufs-qcom.h                   |  32 +--
 8 files changed, 176 insertions(+), 454 deletions(-)
 delete mode 100644 drivers/ufs/host/ufs-qcom-ice.c

Comments

Ulf Hansson April 17, 2023, 8:47 a.m. UTC | #1
On Sat, 8 Apr 2023 at 23:40, Abel Vesa <abel.vesa@linaro.org> wrote:
>
> Now that there is a new dedicated ICE driver, drop the sdhci-msm ICE
> implementation and use the new ICE api provided by the Qualcomm soc
> driver ice. The platforms that already have ICE support will use the
> API as library since there will not be a devicetree node, but instead
> they have reg range. In this case, the of_qcom_ice_get will return an
> ICE instance created for the consumer's device. But if there are
> platforms that do not have ice reg in the consumer devicetree node
> and instead provide a dedicated ICE devicetree node, theof_qcom_ice_get
> will look up the device based on qcom,ice property and will get the ICE
> instance registered by the probe function of the ice driver.
>
> The ICE clock is now handle by the new driver. This is done by enabling
> it on the creation of the ICE instance and then enabling/disabling it on
> SDCC runtime resume/suspend.
>
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>

Acked-by: Ulf Hansson <ulf.hansson@linaro.org>

Bjorn, I think it should be easier if you pick this together with qcom
soc driver changes. I don't think there is any conflict with changes
in my mmc tree.

Otherwise, I will just wait for the next release cycle.

Kind regards
Uffe

> ---
>
> The v6 is here:
> https://lore.kernel.org/all/20230407105029.2274111-6-abel.vesa@linaro.org/
>
> Changes since v6:
>  * none
>
> Changes since v5:
>  * Reworded the commit message to add information about what happens
>    with the ICE clock and who handles it.
>  * Added temp ice variable to avoid setting the host ice to any value
>    until a valid one is provided.
>  * Dropped the qcom_scm.h include as it is not used anymore now that we
>    moved that to the new ICE driver
>
> Changes since v4:
>  * none
>
> Changes since v3:
>  * added back the checks for and the setting of MMC_CAP2_CRYPTO
>  * added enable/resume/suspend implementation for !CONFIG_MMC_CRYPTO
>  * dropped cfg->crypto_cap_idx argument from qcom_ice_program_key
>
> Changes since v2:
>  * added the suspend API call for ICE
>  * kept old wrappers over ICE API in
>
> Changes since v1:
>  * Added a check for supported algorithm and key size
>    and passed the ICE defined values for algorithm and key size
>  * Added call to evict function
>
>  drivers/mmc/host/Kconfig     |   2 +-
>  drivers/mmc/host/sdhci-msm.c | 223 ++++++++---------------------------
>  2 files changed, 48 insertions(+), 177 deletions(-)
>
> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> index 4745fe217ade..09f837df5435 100644
> --- a/drivers/mmc/host/Kconfig
> +++ b/drivers/mmc/host/Kconfig
> @@ -549,7 +549,7 @@ config MMC_SDHCI_MSM
>         depends on MMC_SDHCI_PLTFM
>         select MMC_SDHCI_IO_ACCESSORS
>         select MMC_CQHCI
> -       select QCOM_SCM if MMC_CRYPTO
> +       select QCOM_INLINE_CRYPTO_ENGINE if MMC_CRYPTO
>         help
>           This selects the Secure Digital Host Controller Interface (SDHCI)
>           support present in Qualcomm SOCs. The controller supports
> diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c
> index 8ac81d57a3df..98171bf5748c 100644
> --- a/drivers/mmc/host/sdhci-msm.c
> +++ b/drivers/mmc/host/sdhci-msm.c
> @@ -13,12 +13,13 @@
>  #include <linux/pm_opp.h>
>  #include <linux/slab.h>
>  #include <linux/iopoll.h>
> -#include <linux/firmware/qcom/qcom_scm.h>
>  #include <linux/regulator/consumer.h>
>  #include <linux/interconnect.h>
>  #include <linux/pinctrl/consumer.h>
>  #include <linux/reset.h>
>
> +#include <soc/qcom/ice.h>
> +
>  #include "sdhci-cqhci.h"
>  #include "sdhci-pltfm.h"
>  #include "cqhci.h"
> @@ -258,12 +259,14 @@ struct sdhci_msm_variant_info {
>  struct sdhci_msm_host {
>         struct platform_device *pdev;
>         void __iomem *core_mem; /* MSM SDCC mapped address */
> -       void __iomem *ice_mem;  /* MSM ICE mapped address (if available) */
>         int pwr_irq;            /* power irq */
>         struct clk *bus_clk;    /* SDHC bus voter clock */
>         struct clk *xo_clk;     /* TCXO clk needed for FLL feature of cm_dll*/
> -       /* core, iface, cal, sleep, and ice clocks */
> -       struct clk_bulk_data bulk_clks[5];
> +       /* core, iface, cal and sleep clocks */
> +       struct clk_bulk_data bulk_clks[4];
> +#ifdef CONFIG_MMC_CRYPTO
> +       struct qcom_ice *ice;
> +#endif
>         unsigned long clk_rate;
>         struct mmc_host *mmc;
>         bool use_14lpp_dll_reset;
> @@ -1804,164 +1807,51 @@ static void sdhci_msm_set_clock(struct sdhci_host *host, unsigned int clock)
>
>  #ifdef CONFIG_MMC_CRYPTO
>
> -#define AES_256_XTS_KEY_SIZE                   64
> -
> -/* QCOM ICE registers */
> -
> -#define QCOM_ICE_REG_VERSION                   0x0008
> -
> -#define QCOM_ICE_REG_FUSE_SETTING              0x0010
> -#define QCOM_ICE_FUSE_SETTING_MASK             0x1
> -#define QCOM_ICE_FORCE_HW_KEY0_SETTING_MASK    0x2
> -#define QCOM_ICE_FORCE_HW_KEY1_SETTING_MASK    0x4
> -
> -#define QCOM_ICE_REG_BIST_STATUS               0x0070
> -#define QCOM_ICE_BIST_STATUS_MASK              0xF0000000
> -
> -#define QCOM_ICE_REG_ADVANCED_CONTROL          0x1000
> -
> -#define sdhci_msm_ice_writel(host, val, reg)   \
> -       writel((val), (host)->ice_mem + (reg))
> -#define sdhci_msm_ice_readl(host, reg) \
> -       readl((host)->ice_mem + (reg))
> -
> -static bool sdhci_msm_ice_supported(struct sdhci_msm_host *msm_host)
> -{
> -       struct device *dev = mmc_dev(msm_host->mmc);
> -       u32 regval = sdhci_msm_ice_readl(msm_host, QCOM_ICE_REG_VERSION);
> -       int major = regval >> 24;
> -       int minor = (regval >> 16) & 0xFF;
> -       int step = regval & 0xFFFF;
> -
> -       /* For now this driver only supports ICE version 3. */
> -       if (major != 3) {
> -               dev_warn(dev, "Unsupported ICE version: v%d.%d.%d\n",
> -                        major, minor, step);
> -               return false;
> -       }
> -
> -       dev_info(dev, "Found QC Inline Crypto Engine (ICE) v%d.%d.%d\n",
> -                major, minor, step);
> -
> -       /* If fuses are blown, ICE might not work in the standard way. */
> -       regval = sdhci_msm_ice_readl(msm_host, QCOM_ICE_REG_FUSE_SETTING);
> -       if (regval & (QCOM_ICE_FUSE_SETTING_MASK |
> -                     QCOM_ICE_FORCE_HW_KEY0_SETTING_MASK |
> -                     QCOM_ICE_FORCE_HW_KEY1_SETTING_MASK)) {
> -               dev_warn(dev, "Fuses are blown; ICE is unusable!\n");
> -               return false;
> -       }
> -       return true;
> -}
> -
> -static inline struct clk *sdhci_msm_ice_get_clk(struct device *dev)
> -{
> -       return devm_clk_get(dev, "ice");
> -}
> -
>  static int sdhci_msm_ice_init(struct sdhci_msm_host *msm_host,
>                               struct cqhci_host *cq_host)
>  {
>         struct mmc_host *mmc = msm_host->mmc;
>         struct device *dev = mmc_dev(mmc);
> -       struct resource *res;
> +       struct qcom_ice *ice;
>
>         if (!(cqhci_readl(cq_host, CQHCI_CAP) & CQHCI_CAP_CS))
>                 return 0;
>
> -       res = platform_get_resource_byname(msm_host->pdev, IORESOURCE_MEM,
> -                                          "ice");
> -       if (!res) {
> -               dev_warn(dev, "ICE registers not found\n");
> -               goto disable;
> -       }
> -
> -       if (!qcom_scm_ice_available()) {
> -               dev_warn(dev, "ICE SCM interface not found\n");
> -               goto disable;
> +       ice = of_qcom_ice_get(dev);
> +       if (ice == ERR_PTR(-EOPNOTSUPP)) {
> +               dev_warn(dev, "Disabling inline encryption support\n");
> +               ice = NULL;
>         }
>
> -       msm_host->ice_mem = devm_ioremap_resource(dev, res);
> -       if (IS_ERR(msm_host->ice_mem))
> -               return PTR_ERR(msm_host->ice_mem);
> -
> -       if (!sdhci_msm_ice_supported(msm_host))
> -               goto disable;
> +       if (IS_ERR_OR_NULL(ice))
> +               return PTR_ERR_OR_ZERO(ice);
>
> +       msm_host->ice = ice;
>         mmc->caps2 |= MMC_CAP2_CRYPTO;
> -       return 0;
>
> -disable:
> -       dev_warn(dev, "Disabling inline encryption support\n");
>         return 0;
>  }
>
> -static void sdhci_msm_ice_low_power_mode_enable(struct sdhci_msm_host *msm_host)
> -{
> -       u32 regval;
> -
> -       regval = sdhci_msm_ice_readl(msm_host, QCOM_ICE_REG_ADVANCED_CONTROL);
> -       /*
> -        * Enable low power mode sequence
> -        * [0]-0, [1]-0, [2]-0, [3]-E, [4]-0, [5]-0, [6]-0, [7]-0
> -        */
> -       regval |= 0x7000;
> -       sdhci_msm_ice_writel(msm_host, regval, QCOM_ICE_REG_ADVANCED_CONTROL);
> -}
> -
> -static void sdhci_msm_ice_optimization_enable(struct sdhci_msm_host *msm_host)
> +static void sdhci_msm_ice_enable(struct sdhci_msm_host *msm_host)
>  {
> -       u32 regval;
> -
> -       /* ICE Optimizations Enable Sequence */
> -       regval = sdhci_msm_ice_readl(msm_host, QCOM_ICE_REG_ADVANCED_CONTROL);
> -       regval |= 0xD807100;
> -       /* ICE HPG requires delay before writing */
> -       udelay(5);
> -       sdhci_msm_ice_writel(msm_host, regval, QCOM_ICE_REG_ADVANCED_CONTROL);
> -       udelay(5);
> +       if (msm_host->mmc->caps2 & MMC_CAP2_CRYPTO)
> +               qcom_ice_enable(msm_host->ice);
>  }
>
> -/*
> - * Wait until the ICE BIST (built-in self-test) has completed.
> - *
> - * This may be necessary before ICE can be used.
> - *
> - * Note that we don't really care whether the BIST passed or failed; we really
> - * just want to make sure that it isn't still running.  This is because (a) the
> - * BIST is a FIPS compliance thing that never fails in practice, (b) ICE is
> - * documented to reject crypto requests if the BIST fails, so we needn't do it
> - * in software too, and (c) properly testing storage encryption requires testing
> - * the full storage stack anyway, and not relying on hardware-level self-tests.
> - */
> -static int sdhci_msm_ice_wait_bist_status(struct sdhci_msm_host *msm_host)
> +static __maybe_unused int sdhci_msm_ice_resume(struct sdhci_msm_host *msm_host)
>  {
> -       u32 regval;
> -       int err;
> +       if (msm_host->mmc->caps2 & MMC_CAP2_CRYPTO)
> +               return qcom_ice_resume(msm_host->ice);
>
> -       err = readl_poll_timeout(msm_host->ice_mem + QCOM_ICE_REG_BIST_STATUS,
> -                                regval, !(regval & QCOM_ICE_BIST_STATUS_MASK),
> -                                50, 5000);
> -       if (err)
> -               dev_err(mmc_dev(msm_host->mmc),
> -                       "Timed out waiting for ICE self-test to complete\n");
> -       return err;
> +       return 0;
>  }
>
> -static void sdhci_msm_ice_enable(struct sdhci_msm_host *msm_host)
> +static __maybe_unused int sdhci_msm_ice_suspend(struct sdhci_msm_host *msm_host)
>  {
> -       if (!(msm_host->mmc->caps2 & MMC_CAP2_CRYPTO))
> -               return;
> -       sdhci_msm_ice_low_power_mode_enable(msm_host);
> -       sdhci_msm_ice_optimization_enable(msm_host);
> -       sdhci_msm_ice_wait_bist_status(msm_host);
> -}
> +       if (msm_host->mmc->caps2 & MMC_CAP2_CRYPTO)
> +               return qcom_ice_suspend(msm_host->ice);
>
> -static int __maybe_unused sdhci_msm_ice_resume(struct sdhci_msm_host *msm_host)
> -{
> -       if (!(msm_host->mmc->caps2 & MMC_CAP2_CRYPTO))
> -               return 0;
> -       return sdhci_msm_ice_wait_bist_status(msm_host);
> +       return 0;
>  }
>
>  /*
> @@ -1972,48 +1862,28 @@ static int sdhci_msm_program_key(struct cqhci_host *cq_host,
>                                  const union cqhci_crypto_cfg_entry *cfg,
>                                  int slot)
>  {
> -       struct device *dev = mmc_dev(cq_host->mmc);
> +       struct sdhci_host *host = mmc_priv(cq_host->mmc);
> +       struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host);
> +       struct sdhci_msm_host *msm_host = sdhci_pltfm_priv(pltfm_host);
>         union cqhci_crypto_cap_entry cap;
> -       union {
> -               u8 bytes[AES_256_XTS_KEY_SIZE];
> -               u32 words[AES_256_XTS_KEY_SIZE / sizeof(u32)];
> -       } key;
> -       int i;
> -       int err;
> -
> -       if (!(cfg->config_enable & CQHCI_CRYPTO_CONFIGURATION_ENABLE))
> -               return qcom_scm_ice_invalidate_key(slot);
>
>         /* Only AES-256-XTS has been tested so far. */
>         cap = cq_host->crypto_cap_array[cfg->crypto_cap_idx];
>         if (cap.algorithm_id != CQHCI_CRYPTO_ALG_AES_XTS ||
> -           cap.key_size != CQHCI_CRYPTO_KEY_SIZE_256) {
> -               dev_err_ratelimited(dev,
> -                                   "Unhandled crypto capability; algorithm_id=%d, key_size=%d\n",
> -                                   cap.algorithm_id, cap.key_size);
> +               cap.key_size != CQHCI_CRYPTO_KEY_SIZE_256)
>                 return -EINVAL;
> -       }
>
> -       memcpy(key.bytes, cfg->crypto_key, AES_256_XTS_KEY_SIZE);
> -
> -       /*
> -        * The SCM call byte-swaps the 32-bit words of the key.  So we have to
> -        * do the same, in order for the final key be correct.
> -        */
> -       for (i = 0; i < ARRAY_SIZE(key.words); i++)
> -               __cpu_to_be32s(&key.words[i]);
> -
> -       err = qcom_scm_ice_set_key(slot, key.bytes, AES_256_XTS_KEY_SIZE,
> -                                  QCOM_SCM_ICE_CIPHER_AES_256_XTS,
> -                                  cfg->data_unit_size);
> -       memzero_explicit(&key, sizeof(key));
> -       return err;
> +       if (cfg->config_enable & CQHCI_CRYPTO_CONFIGURATION_ENABLE)
> +               return qcom_ice_program_key(msm_host->ice,
> +                                           QCOM_ICE_CRYPTO_ALG_AES_XTS,
> +                                           QCOM_ICE_CRYPTO_KEY_SIZE_256,
> +                                           cfg->crypto_key,
> +                                           cfg->data_unit_size, slot);
> +       else
> +               return qcom_ice_evict_key(msm_host->ice, slot);
>  }
> +
>  #else /* CONFIG_MMC_CRYPTO */
> -static inline struct clk *sdhci_msm_ice_get_clk(struct device *dev)
> -{
> -       return NULL;
> -}
>
>  static inline int sdhci_msm_ice_init(struct sdhci_msm_host *msm_host,
>                                      struct cqhci_host *cq_host)
> @@ -2025,11 +1895,17 @@ static inline void sdhci_msm_ice_enable(struct sdhci_msm_host *msm_host)
>  {
>  }
>
> -static inline int __maybe_unused
> +static inline __maybe_unused int
>  sdhci_msm_ice_resume(struct sdhci_msm_host *msm_host)
>  {
>         return 0;
>  }
> +
> +static inline __maybe_unused int
> +sdhci_msm_ice_suspend(struct sdhci_msm_host *msm_host)
> +{
> +       return 0;
> +}
>  #endif /* !CONFIG_MMC_CRYPTO */
>
>  /*****************************************************************************\
> @@ -2630,11 +2506,6 @@ static int sdhci_msm_probe(struct platform_device *pdev)
>                 clk = NULL;
>         msm_host->bulk_clks[3].clk = clk;
>
> -       clk = sdhci_msm_ice_get_clk(&pdev->dev);
> -       if (IS_ERR(clk))
> -               clk = NULL;
> -       msm_host->bulk_clks[4].clk = clk;
> -
>         ret = clk_bulk_prepare_enable(ARRAY_SIZE(msm_host->bulk_clks),
>                                       msm_host->bulk_clks);
>         if (ret)
> @@ -2827,7 +2698,7 @@ static __maybe_unused int sdhci_msm_runtime_suspend(struct device *dev)
>         clk_bulk_disable_unprepare(ARRAY_SIZE(msm_host->bulk_clks),
>                                    msm_host->bulk_clks);
>
> -       return 0;
> +       return sdhci_msm_ice_suspend(msm_host);
>  }
>
>  static __maybe_unused int sdhci_msm_runtime_resume(struct device *dev)
> --
> 2.34.1
>
Krzysztof Kozlowski May 5, 2023, 6:47 p.m. UTC | #2
On 08/04/2023 23:40, Abel Vesa wrote:
> Starting with SM8550, the ICE will have its own devicetree node
> so add the qcom,ice property to reference it.
> 
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
> 
> The v6 is here:
> https://lore.kernel.org/all/20230407105029.2274111-3-abel.vesa@linaro.org/
> 
> Changes since v6:
>  * Dropped the minItems for both the qcom,ice and the reg in the
>    qcom,ice compatile subschema, like Krzysztof suggested
> 
> Changes since v5:
>  * dropped the sm8550 specific subschema and replaced it with one that
>    mutually excludes the qcom,ice vs both the ICE specific reg range
>    and the ICE clock
> 
> Changes since v4:
>  * Added check for sm8550 compatible w.r.t. qcom,ice in order to enforce
>    it while making sure none of the other platforms are allowed to use it
> 
> Changes since v3:
>  * dropped the "and drop core clock" part from subject line
> 
> Changes since v2:
>  * dropped all changes except the qcom,ice property
> 
> 
>  .../devicetree/bindings/ufs/qcom,ufs.yaml     | 24 +++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 

I see dt_binding_check errors after applying this patch. Are you sure
this was tested?

Best regards,
Krzysztof
Krzysztof Kozlowski June 18, 2023, 8:53 a.m. UTC | #3
On 08/04/2023 23:40, Abel Vesa wrote:
> Starting with SM8550, the ICE will have its own devicetree node
> so add the qcom,ice property to reference it.
> 
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
> 
> The v6 is here:
> https://lore.kernel.org/all/20230407105029.2274111-3-abel.vesa@linaro.org/
> 
> Changes since v6:
>  * Dropped the minItems for both the qcom,ice and the reg in the
>    qcom,ice compatile subschema, like Krzysztof suggested
> 
> Changes since v5:
>  * dropped the sm8550 specific subschema and replaced it with one that
>    mutually excludes the qcom,ice vs both the ICE specific reg range
>    and the ICE clock
> 
> Changes since v4:
>  * Added check for sm8550 compatible w.r.t. qcom,ice in order to enforce
>    it while making sure none of the other platforms are allowed to use it
> 
> Changes since v3:
>  * dropped the "and drop core clock" part from subject line
> 
> Changes since v2:
>  * dropped all changes except the qcom,ice property
> 
> 
>  .../devicetree/bindings/ufs/qcom,ufs.yaml     | 24 +++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml b/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
> index c5a06c048389..10d426ba1959 100644
> --- a/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
> +++ b/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
> @@ -70,6 +70,10 @@ properties:
>    power-domains:
>      maxItems: 1
>  
> +  qcom,ice:
> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description: phandle to the Inline Crypto Engine node
> +
>    reg:
>      minItems: 1
>      maxItems: 2
> @@ -187,6 +191,26 @@ allOf:
>  
>      # TODO: define clock bindings for qcom,msm8994-ufshc
>  
> +  - if:
> +      properties:
> +        qcom,ice:

Un-reviewed. This is broken and was never tested. After applying this
patch, I can see many new warnings in all DTBs (so it is easy to spot
that it was not actually tested).

Your probably meant here:
  if:
    required:


Best regards,
Krzysztof
Martin K. Petersen June 22, 2023, 1:19 a.m. UTC | #4
Abel,

> Un-reviewed. This is broken and was never tested. After applying this
> patch, I can see many new warnings in all DTBs (so it is easy to spot
> that it was not actually tested).
>
> Your probably meant here:
>   if:
>     required:

Please provide a fix for this. I don't want to rebase this late in the
cycle.

Thanks!
Krzysztof Kozlowski June 22, 2023, 6:07 a.m. UTC | #5
On 22/06/2023 03:19, Martin K. Petersen wrote:
> 
> Abel,
> 
>> Un-reviewed. This is broken and was never tested. After applying this
>> patch, I can see many new warnings in all DTBs (so it is easy to spot
>> that it was not actually tested).
>>
>> Your probably meant here:
>>   if:
>>     required:
> 
> Please provide a fix for this. I don't want to rebase this late in the
> cycle.

AFAIK, this was not applied. At least as of next 20210621 and I
commented on this few days ago. Anything changed here?

Best regards,
Krzysztof
Abel Vesa June 22, 2023, 7:02 a.m. UTC | #6
On 23-06-22 08:07:51, Krzysztof Kozlowski wrote:
> On 22/06/2023 03:19, Martin K. Petersen wrote:
> > 
> > Abel,
> > 
> >> Un-reviewed. This is broken and was never tested. After applying this
> >> patch, I can see many new warnings in all DTBs (so it is easy to spot
> >> that it was not actually tested).
> >>
> >> Your probably meant here:
> >>   if:
> >>     required:
> > 
> > Please provide a fix for this. I don't want to rebase this late in the
> > cycle.
> 
> AFAIK, this was not applied. At least as of next 20210621 and I
> commented on this few days ago. Anything changed here?

Check this one:
https://lore.kernel.org/all/yq1a5x1wl4g.fsf@ca-mkp.ca.oracle.com/

I'll send a fix today.

> 
> Best regards,
> Krzysztof
>
Krzysztof Kozlowski June 22, 2023, 9:28 a.m. UTC | #7
On 22/06/2023 09:02, Abel Vesa wrote:
> On 23-06-22 08:07:51, Krzysztof Kozlowski wrote:
>> On 22/06/2023 03:19, Martin K. Petersen wrote:
>>>
>>> Abel,
>>>
>>>> Un-reviewed. This is broken and was never tested. After applying this
>>>> patch, I can see many new warnings in all DTBs (so it is easy to spot
>>>> that it was not actually tested).
>>>>
>>>> Your probably meant here:
>>>>   if:
>>>>     required:
>>>
>>> Please provide a fix for this. I don't want to rebase this late in the
>>> cycle.
>>
>> AFAIK, this was not applied. At least as of next 20210621 and I
>> commented on this few days ago. Anything changed here?
> 
> Check this one:
> https://lore.kernel.org/all/yq1a5x1wl4g.fsf@ca-mkp.ca.oracle.com/
> 

So staging tree is not in next? If it cannot be rebased "that late in
the cycle", this means it should be in the next. :/

Best regards,
Krzysztof
Martin K. Petersen June 23, 2023, 1:06 a.m. UTC | #8
Hi Krzysztof!

> AFAIK, this was not applied. At least as of next 20210621 and I
> commented on this few days ago. Anything changed here?

It's definitely there in 20230621:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml?h=next-20230621

I merged the series on the 16th prior to you withdrawing your
Reviewed-by: tag. But let's just get the bindings fixed.