[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54893963.7060304@ti.com>
Date: Thu, 11 Dec 2014 11:57:47 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Joe Perches <joe@...ches.com>
CC: Yunzhi Li <lyz@...k-chips.com>, <heiko@...ech.de>,
<jwerner@...omium.org>, <dianders@...omium.org>, <olof@...om.net>,
<huangtao@...k-chips.com>, <zyw@...k-chips.com>,
<cf@...k-chips.com>, <linux-rockchip@...ts.infradead.org>,
Grant Likely <grant.likely@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>
Subject: Re: [PATCH v5 1/5] phy: add a driver for the Rockchip SoC internal
USB2.0 PHY
Hi,
On Thursday 11 December 2014 11:42 AM, Joe Perches wrote:
> On Thu, 2014-12-11 at 11:32 +0530, Kishon Vijay Abraham I wrote:
>> On Wednesday 10 December 2014 04:16 PM, Yunzhi Li wrote:
>>> diff --git a/drivers/phy/phy-rockchip-usb.c b/drivers/phy/phy-rockchip-usb.c
> []
>>> +/*
>>> + * The higher 16-bit of this register is used for write protection
>>> + * only if BIT(13 + 16) set to 1 the BIT(13) can be written.
>>> + */
>>> +#define SIDDQ_MSK BIT(13 + 16)
>
> huh?
>
> This #define looks _very_ odd.
>
> Is this supposed to be a single bit 29 or
> some range?
>From what I understood, the most significant 16 bits are write locks to the
least significant 16 bits.
So If I have to write something on bit 0, I have to set bit 16.
If I have to write something on bit 1, I have to set bit 17.
If I have to write something on bit 2, I have to set bit 18.
and so on.
Thanks
Kishon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists