[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CABHD4K9awH3moyCktEq3acYN=GS74nhThuFDsYt10UTqOHSw3Q@mail.gmail.com>
Date: Sun, 31 Jul 2016 18:09:12 +0530
From: Amit Tomer <amittomer25@...il.com>
To: Icenowy Zheng <icenowy@...c.xyz>
Cc: Rob Herring <robh+dt@...nel.org>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>,
Hans de Goede <hdegoede@...hat.com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-usb@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Reinder de Haan <patchesrdh@...as.com>,
linux-kernel@...r.kernel.org,
Kishon Vijay Abraham I <kishon@...com>,
Tony Prisk <linux@...sktech.co.nz>,
Alan Stern <stern@...land.harvard.edu>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/3] phy: sun4i: add support for A64 usb phy
Hello ,
> @@ -264,6 +266,12 @@ static int sun4i_usb_phy_init(struct phy *_phy)
> val = readl(phy->pmu + REG_PMU_UNK_H3);
> writel(val & ~2, phy->pmu + REG_PMU_UNK_H3);
> } else {
> + /* A64 needs also this unknown bit */
> + if (data->cfg->type == sun50i_a64_phy) {
> + val = readl(phy->pmu + REG_PMU_UNK_H3);
> + writel(val & ~2, phy->pmu + REG_PMU_UNK_H3);
> + }
> +
This bit is also set for H3, shall we reuse it or we should enclose it
in else-if part ?
Thanks
Amit.
Powered by blists - more mailing lists