[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11daa581-65c2-47d5-8bd3-78757fd55ee3@novek.ru>
Date: Mon, 27 Jun 2022 23:04:48 +0100
From: Vadim Fedorenko <vfedorenko@...ek.ru>
To: Jonathan Lemon <jonathan.lemon@...il.com>
Cc: Jakub Kicinski <kuba@...nel.org>, Vadim Fedorenko <vadfed@...com>,
Aya Levin <ayal@...dia.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH v1 3/3] ptp_ocp: implement DPLL ops
On 27.06.2022 20:23, Jonathan Lemon wrote:
> On Sun, Jun 26, 2022 at 08:27:17PM +0100, Vadim Fedorenko wrote:
>> On 23.06.2022 19:28, Jonathan Lemon wrote:
>>> On Thu, Jun 23, 2022 at 03:57:17AM +0300, Vadim Fedorenko wrote:
>>>> From: Vadim Fedorenko <vadfed@...com>
>>>>
>>>> +static int ptp_ocp_dpll_get_status(struct dpll_device *dpll)
>>>> +{
>>>> + struct ptp_ocp *bp = (struct ptp_ocp *)dpll_priv(dpll);
>>>> + int sync;
>>>> +
>>>> + sync = ioread32(&bp->reg->status) & OCP_STATUS_IN_SYNC;
>>>> + return sync;
>>>> +}
>>>
>>> Please match existing code style.
>>>
>>
>> Didn't get this point. The same code is used through out the driver.
>> Could you please explain?
>
> Match existing function definition style.
Got it. Will address in the next version, thanks!
Powered by blists - more mailing lists