linux-kernel - Re: Reset implementation for Zynq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKfKVtGnpdBsqtV2fEg2jk5v5XZtGULx-hc5waUKqUq_xRCp9w@mail.gmail.com>
Date:   Tue, 8 Nov 2016 12:04:53 +0530
From:   Shubhrajyoti Datta <shubhrajyoti.datta@...il.com>
To:     Moritz Fischer <moritz.fischer@...us.com>
Cc:     iztok.jeras@...pitaya.com, p.zabel@...gutronix.de,
        linux-kernel@...r.kernel.org
Subject: Re: Reset implementation for Zynq

On Fri, Oct 21, 2016 at 10:34 PM, Moritz Fischer
<moritz.fischer@...us.com> wrote:
> Iztok,
>
> On Fri, Oct 21, 2016 at 03:08:47AM -0700, iztok.jeras@...pitaya.com wrote:
>> Hi Moritz,
>>
>> I was looking at your reset implementation for Zynq:
>> https://github.com/Xilinx/linux-xlnx/blob/629041605b93343ad2e8971ceaac3edcef0b043b/drivers/reset/reset-zynq.c
>> I went through related mailing list posts (including earlier versions of the patch) so I kind of understand what to change in the device tree.
>
> Please look at the upstream kernel sources and use the mailing list
> (lkml) if you want to report bugs. Xilinx' vendor tree might or might
> not be up to date.
>
>> I would like to use this driver to reset the Zynq I2C controller, since we have trouble with it getting into a lock up state.

Can you explain what you are facing and what is meant by lockup state.