From: Tzu-Hao Wei <twei@axiado.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: SriNavmani A <srinavmani@axiado.com>,
Prasad Bolisetty <pbolisetty@axiado.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH v2 2/4] phy: axiado: add Axiado eMMC PHY driver
Date: Mon, 2 Mar 2026 10:02:53 -0800 [thread overview]
Message-ID: <e1628331-9fa2-4471-b7a2-4df5d34ce873@axiado.com> (raw)
In-Reply-To: <aaGv3q8czkrKyW42@vaman>
On 2/27/2026 6:53 AM, Vinod Koul wrote:
>> --- /dev/null
>> +++ b/drivers/phy/axiado/phy-axiado-emmc.c
>> @@ -0,0 +1,221 @@
>> +// SPDX-License-Identifier: GPL-2.0-or-later
>> +/*
>> + * Axiado eMMC PHY driver
>> + *
>> + * Copyright (C) 2017 Arasan Chip Systems Inc.
>> + * Copyright (C) 2022-2025 Axiado Corporation (or its affiliates).
>
> 2026
>
Thanks. Will fix in the next version.
>> + *
>> + * Based on Arasan Driver (sdhci-pci-arasan.c)
>> + * sdhci-pci-arasan.c - Driver for Arasan PCI Controller with integrated phy.
>> + */
>> +#include <linux/bitfield.h>
>> +#include <linux/delay.h>
>> +#include <linux/io.h>
>> +#include <linux/iopoll.h>
>> +#include <linux/module.h>
>> +#include <linux/of.h>
>> +#include <linux/phy/phy.h>
>> +#include <linux/platform_device.h>
>> +
>> +/* Arasan eMMC 5.1 - PHY configuration registers */
>> +#define CAP_REG_IN_S1_LSB 0x00
>> +#define CAP_REG_IN_S1_MSB 0x04
>> +#define PHY_CTRL_1 0x38
>> +#define PHY_CTRL_2 0x3C
>
> smaller hex case please, here and other places
>
Thanks. Will fix in the next version.
>> +#define PHY_CTRL_3 0x40
>> +#define STATUS 0x50
>> +
>> +#define DLL_ENBL BIT(26)
>> +#define RTRIM_EN BIT(21)
>> +#define PDB_ENBL BIT(23)
>> +#define RETB_ENBL BIT(1)
>> +
>> +#define REN_STRB BIT(27)
>> +#define REN_CMD BIT(12)
>> +#define REN_DAT0 BIT(13)
>> +#define REN_DAT1 BIT(14)
>> +#define REN_DAT2 BIT(15)
>> +#define REN_DAT3 BIT(16)
>> +#define REN_DAT4 BIT(17)
>> +#define REN_DAT5 BIT(18)
>> +#define REN_DAT6 BIT(19)
>> +#define REN_DAT7 BIT(20)
>> +#define REN_CMD_EN (REN_CMD | REN_DAT0 | REN_DAT1 | REN_DAT2 | \
>> + REN_DAT3 | REN_DAT4 | REN_DAT5 | REN_DAT6 | REN_DAT7)
>> +
>> +/* Pull-UP Enable on CMD Line */
>> +#define PU_CMD BIT(3)
>> +#define PU_DAT0 BIT(4)
>> +#define PU_DAT1 BIT(5)
>> +#define PU_DAT2 BIT(6)
>> +#define PU_DAT3 BIT(7)
>> +#define PU_DAT4 BIT(8)
>> +#define PU_DAT5 BIT(9)
>> +#define PU_DAT6 BIT(10)
>> +#define PU_DAT7 BIT(11)
>> +#define PU_CMD_EN (PU_CMD | PU_DAT0 | PU_DAT1 | PU_DAT2 | PU_DAT3 | \
>> + PU_DAT4 | PU_DAT5 | PU_DAT6 | PU_DAT7)
>
> The bit define are used only once, why not define the cmd with
> respective bits here
>
Will replace it by
#define PU_CMD_EN GENMASK(11, 3)
>> +static const struct phy_ops axiado_emmc_phy_ops = {
>> + .init = axiado_emmc_phy_init,
>> + .power_on = axiado_emmc_phy_power_on,
>
> no power_off?
>
Thanks for reminding, will add power_off.
> --
> ~Vinod
next prev parent reply other threads:[~2026-03-02 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 8:22 [PATCH v2 0/4] Add eMMC PHY support for Axiado AX3000 SoC Tzu-Hao Wei
2026-02-06 8:22 ` [PATCH v2 1/4] dt-bindings: phy: axiado,ax3000-emmc-phy: add Axiado eMMC PHY Tzu-Hao Wei
2026-02-10 1:30 ` Rob Herring (Arm)
2026-02-06 8:22 ` [PATCH v2 2/4] phy: axiado: add Axiado eMMC PHY driver Tzu-Hao Wei
2026-02-27 14:53 ` Vinod Koul
2026-03-02 18:02 ` Tzu-Hao Wei [this message]
2026-02-06 8:22 ` [PATCH v2 3/4] MAINTAINERS: Add Axiado AX3000 " Tzu-Hao Wei
2026-02-06 8:22 ` [PATCH v2 4/4] arm64: dts: axiado: Add eMMC PHY node Tzu-Hao Wei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1628331-9fa2-4471-b7a2-4df5d34ce873@axiado.com \
--to=twei@axiado.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pbolisetty@axiado.com \
--cc=robh@kernel.org \
--cc=srinavmani@axiado.com \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®