Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1044531ybt; Wed, 1 Jul 2020 17:12:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyuoFM/fJ6+je8573lWf5HeYhox+amieJA5/5p76DwOYf3ASU7RoZH55qsmToKN/+J56yAv X-Received: by 2002:a17:906:4a87:: with SMTP id x7mr25579965eju.44.1593648721079; Wed, 01 Jul 2020 17:12:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593648721; cv=none; d=google.com; s=arc-20160816; b=KJXmVfIToGGTZgxar5Ck86UA76fteuOypfIGmKhkia1wbWg4lM6bEeyxCWrJhTFUiH bRfgaubLXDlNKN590tU+NmA/SlkqaTEN/JhOTrMzq9KS2QXSAcyOBgKnXTXD9W9yN1Sj vPO51sOldNk0JLPKiJ7Oi1WvRPLYv+305a2Kq+S0sGHJRf1kJbFEfzieaVqHJlkweVm5 z+JSb87tdBMSVLXDyWZwktJ835XPgrFJALIiQce1DvfpUWbihy8w323Zy/zLtTL5w+Gn 8KCL+8DkXMwOgSZgZrVXrowq66RP6TpCLDdc24SuhzWGOmGiYRTrVMKW/B0c/rgA6+bn L36w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :ironport-sdr:ironport-sdr; bh=U7YUbnvFIUpAmyIRzX5lIeLr/Uf93OXs5Zt3s4OEYrA=; b=wjB5/tKK0GPmP0UJ3/TKbIIHP0FW/VxlIL6HUjsHAO39N68pCT295lotO3fJL/17cc ndUmxvlnyu49lUWVPmHDmoFUoChtBIv/XNelYzKbx8HLu+nRz0xzAk/vQeLZbMVuT8UQ pQEminmNzV1sW9fFLhf/7H8p6lIEpyIIRp19tPk+eXoqsP/RFnXO9kLQk5sbsken9hKi idxxA3WU1zNKH5MUmq0qtK2URmaxCWPz3gw61bCMpcIbnuP6SQ3rT4NLY9g26uUyP8Sh b9Mm3U/zBbhL7d91cjxBN7Ka2tlabWF90NGhhlsdmEYkyOL2Ts7x1sm9LR0PDIKrZUqp WFdw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dh22si4920445edb.38.2020.07.01.17.11.37; Wed, 01 Jul 2020 17:12:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727917AbgGBAL2 (ORCPT + 99 others); Wed, 1 Jul 2020 20:11:28 -0400 Received: from mga03.intel.com ([134.134.136.65]:60622 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727811AbgGBAL2 (ORCPT ); Wed, 1 Jul 2020 20:11:28 -0400 IronPort-SDR: mRC70VIOh709/gDQPktr5c5EVBeXWf8dIILww1G0TZT9B5vpebY9CFrOkGsJFMZHfI6VpcFRE6 as10eNIKrH8A== X-IronPort-AV: E=McAfee;i="6000,8403,9669"; a="146734362" X-IronPort-AV: E=Sophos;i="5.75,302,1589266800"; d="scan'208";a="146734362" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jul 2020 17:11:27 -0700 IronPort-SDR: I/ump2lWM/lC/2qxq2przIm/+UyuIz8O7/sFbUWqEVbP8X8PekO6jQbH2ek8JNadEeCZAA6qv1 oLwByjRZGpUA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,302,1589266800"; d="scan'208";a="313944369" Received: from wwanmoha-ilbpg2.png.intel.com ([10.88.227.42]) by fmsmga002.fm.intel.com with ESMTP; 01 Jul 2020 17:11:25 -0700 From: Wan Ahmad Zainie To: kishon@ti.com, vkoul@kernel.org, robh+dt@kernel.org, andriy.shevchenko@intel.com Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, wan.ahmad.zainie.wan.mohamad@intel.com, sureshkumar.mp@intel.com, lakshmi.bai.raja.subramanian@intel.com Subject: [PATCH v6 0/2] phy: intel: Add Keem Bay eMMC PHY support Date: Thu, 2 Jul 2020 08:09:32 +0800 Message-Id: <20200702000934.3258-1-wan.ahmad.zainie.wan.mohamad@intel.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi. The first part is to document DT bindings for Keem Bay eMMC PHY. The second is the driver file, loosely based on phy-rockchip-emmc.c and phy-intel-emmc.c. The latter is not being reused as there are quite a number of differences i.e. registers offset, supported clock rates, bitfield to set. The patch was tested with Keem Bay evaluation module board. Thank you. Best regards, Zainie Changes since resend v5: - In keembay_emmc_phy_power(), remove redundant return ret;. Resend v5: - Include missing changes done for phy-keembay-emmc.c (See Changes since v3) Changes since v4: - In Kconfig file, add depends on ARM64 || COMPILE_TEST and depends on OF && HAS_IOMEM. - In Kconfig file, reword the help section to be more verbose. Changes since v3: - Exit keembay_emmc_phy_power() with return ret;. - In keembay_emmc_phy_init(), use PTR_ERR_OR_ZERO(...). - In keembay_emmc_phy_probe(), devm_regmap_init_mmio(...) in single line. Changes since v2: - Modify DT example to use single cell for address and size. Changes since v1: - Rework phy-keembay-emmc.c to make it similar to phy-intel-emmc.c. - Use regmap_mmio, and remove reference to intel,syscon. - Use node name phy@.... - Update license i.e. use dual license. Wan Ahmad Zainie (2): dt-bindings: phy: intel: Add Keem Bay eMMC PHY bindings phy: intel: Add Keem Bay eMMC PHY support .../bindings/phy/intel,keembay-emmc-phy.yaml | 44 +++ drivers/phy/intel/Kconfig | 12 + drivers/phy/intel/Makefile | 1 + drivers/phy/intel/phy-keembay-emmc.c | 314 ++++++++++++++++++ 4 files changed, 371 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/intel,keembay-emmc-phy.yaml create mode 100644 drivers/phy/intel/phy-keembay-emmc.c -- 2.17.1