linux-kernel - Re: [PATCH v6 01/10] i3c: Add core I3C infrastructure

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <E73421F5-DC9B-4000-B282-FF71D7E45866@cadence.com>
Date:   Tue, 4 Sep 2018 11:03:35 +0000
From:   Przemyslaw Gaj <pgaj@...ence.com>
To:     vitor <Vitor.Soares@...opsys.com>,
        Boris Brezillon <boris.brezillon@...tlin.com>
CC:     "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        Sekhar Nori <nsekhar@...com>, Wolfram Sang <wsa@...-dreams.de>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Arnd Bergmann <arnd@...db.de>,
        Przemyslaw Sroka <psroka@...ence.com>,
        Arkadiusz Golec <agolec@...ence.com>,
        Alan Douglas <adouglas@...ence.com>,
        Bartosz Folta <bfolta@...ence.com>,
        Damian Kos <dkos@...ence.com>,
        Alicja Jurasik-Urbaniak <alicja@...ence.com>,
        Cyprian Wronka <cwronka@...ence.com>,
        Suresh Punnoose <sureshp@...ence.com>,
        Rafal Ciepiela <rafalc@...ence.com>,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
        Nishanth Menon <nm@...com>, Rob Herring <robh+dt@...nel.org>,
        Pawel Moll <pawel.moll@....com>,
        Mark Rutland <mark.rutland@....com>,
        Ian Campbell <ijc+devicetree@...lion.org.uk>,
        Kumar Gala <galak@...eaurora.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Xiang Lin <Xiang.Lin@...aptics.com>,
        Peter Rosin <peda@...ntia.se>
Subject: Re: [PATCH v6 01/10] i3c: Add core I3C infrastructure

Hi Vitor,

On 9/3/18, 11:33 AM, "vitor" <Vitor.Soares@...opsys.com> wrote:

    EXTERNAL MAIL
    
    
    Hi Przemek,
    
    
    On 30-08-2018 20:00, Przemyslaw Gaj wrote:
    >      So, per my understanding since the Main master support the hand-off of
    >      the bus you accept all incoming MR, right? Or do you check all devices BCR?
    >
    > I'm not sure what do you mean here. Mastership request(MR) is from secondary master
    > to current master. Current master can NACK this request if for example it comes from
    > wrong device. If it's ok, current master sends GETACCMST command and secondary master
    > may ACK or NACK this command. It it's acked, secondary master becomes current master.
    >      
    >      Best regards,
    >      Vitor Soares
    >
    > Please let me know if something is unclear.
    >
    > Regards,
    > Przemek
    >      
    
    Sorry, it s not clear yet.
    
    For instances there is a bus with several secondary master. If each of 
    them request the bus mastership (one at a time), will you accept all by 
    default? Because you can only accept only some of them.

First of all, only devices which have Mastership request event enabled (ENMR slave event)
can request mastership. Second thing is that this device needs to have IBI enabled in 
current master. I accept all such devices. There is no additional logic for now, we can add it
in the future.

I was very busy recently. I'm almost ready to publish my changes related to mastership request.
I'm sorry for the delay.
    
    Regards,
    Vitor Soares
    
Regards,
Przemek