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;
IronPort-SDR: yJgWcJR9ZBNxFpYzizYj1wpXho34+jQyIIuCMp+voCbSiUdwYTz2GsMORQwNvwJECQLDPWFwVi
 M9LZocYKQ+8A==
IronPort-SDR: qZT80fhhjld5H1CFihUxcNTKuFzHUZmfyeJlsQwfljD3yn6THCLCTW8QhM0fURpH7Be8NbOEId
 3TU7523keGVw==
From:   "Wan Mohamad, Wan Ahmad Zainie" 
        <wan.ahmad.zainie.wan.mohamad@intel.com>
To:     "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
CC:     "kishon@ti.com" <kishon@ti.com>,
        "vkoul@kernel.org" <vkoul@kernel.org>,
        "robh+dt@kernel.org" <robh+dt@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "Hunter, Adrian" <adrian.hunter@intel.com>
Subject: RE: [PATCH v5 2/2] phy: intel: Add Keem Bay eMMC PHY support
Thread-Topic: [PATCH v5 2/2] phy: intel: Add Keem Bay eMMC PHY support
Thread-Index: AQHWQ+wc04c1VDLsCUu4H/RWl0c5TajbcusAgACRWLA=
Date:   Wed, 17 Jun 2020 01:34:50 +0000
Message-ID: <DM6PR11MB3721BFF25B5377B28E56F69DDD9A0@DM6PR11MB3721.namprd11.prod.outlook.com>
References: <20200616143818.13579-1-wan.ahmad.zainie.wan.mohamad@intel.com>
 <20200616143818.13579-3-wan.ahmad.zainie.wan.mohamad@intel.com>
 <20200616164420.GZ2428291@smile.fi.intel.com>
In-Reply-To: <20200616164420.GZ2428291@smile.fi.intel.com>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-reaction: no-action
dlp-version: 11.2.0.6
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a86fdf67-1b60-4950-aa2a-08d8125ea0fa
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jun 2020 01:34:50.9003
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2TqBohwMq9XZaGq/l/5rJiFG4l3KNlOIAiqSNOBYGRvN7rgdNLG4baVQG09iLtVBevVHZLL78SEvOeKax5SLzhTXZ82EWWFapvF5hhCUDQ+djjDZekGPzsx6Nv1aII4K
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4691
X-OriginatorOrg: intel.com
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


> -----Original Message-----
> From: Shevchenko, Andriy <andriy.shevchenko@intel.com>
> Sent: Wednesday, June 17, 2020 12:44 AM
> To: Wan Mohamad, Wan Ahmad Zainie
> <wan.ahmad.zainie.wan.mohamad@intel.com>
> Cc: kishon@ti.com; vkoul@kernel.org; robh+dt@kernel.org; linux-
> kernel@vger.kernel.org; devicetree@vger.kernel.org; Hunter, Adrian
> <adrian.hunter@intel.com>
> Subject: Re: [PATCH v5 2/2] phy: intel: Add Keem Bay eMMC PHY support
>=20
> On Tue, Jun 16, 2020 at 10:38:18PM +0800, Wan Ahmad Zainie wrote:
> > Add support for eMMC PHY on Intel Keem Bay SoC.
>=20
> ...
>=20
> > +	ret =3D regmap_read_poll_timeout(priv->syscfg, PHY_STAT,
> > +				       dllrdy, IS_DLLRDY(dllrdy),
> > +				       0, 50 * USEC_PER_MSEC);
> > +	if (ret) {
> > +		dev_err(&phy->dev, "dllrdy failed, ret=3D%d\n", ret);
>=20
> > +		return ret;
> > +	}
> > +
> > +	return ret;
>=20
> return ret;
>=20
> (Since it's only one minor issue, it's up to maintainers to decide if new
> version is needed)

This was addressed in v4, together with another 2 changes.
I was careless when modifying Kconfig in my older working branch.

I resend v5.

>=20
> --
> With Best Regards,
> Andy Shevchenko
>=20