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: <SN6PR04MB4925A158FB93AC99D15ED3EBFC6F0@SN6PR04MB4925.namprd04.prod.outlook.com>
Date:   Wed, 6 Feb 2019 13:57:17 +0000
From:   Avri Altman <Avri.Altman@....com>
To:     Kishon Vijay Abraham I <kishon@...com>,
        Evan Green <evgreen@...omium.org>,
        Andy Gross <andy.gross@...aro.org>,
        Vinayak Holikatti <vinholikatti@...il.com>
CC:     Stephen Boyd <swboyd@...omium.org>,
        Marc Gonzalez <marc.w.gonzalez@...e.fr>,
        Can Guo <cang@...eaurora.org>,
        Vivek Gautam <vivek.gautam@...eaurora.org>,
        Douglas Anderson <dianders@...omium.org>,
        Asutosh Das <asutoshd@...eaurora.org>,
        "James E.J. Bottomley" <jejb@...ux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 6/8] scsi: ufs: qcom: Expose the reset controller for
 PHY

Hi,

> On 06/02/19 12:29 AM, Evan Green wrote:
> > Expose a reset controller that the phy will later use to control its
> > own PHY reset in the UFS controller. This will enable the combining
> > of PHY init functionality into a single function.
> >
> > Signed-off-by: Evan Green <evgreen@...omium.org>
> 
> I'd like to get ACK from scsi/ufs/ MAINTAINER Vinayak for me merge it in PHY
> tree.
Looks like this series is qcom specific, and has less impact of the ufs core driver.

> > +	err = devm_reset_controller_register(dev, &host->rcdev);
Just my 2 cents:
Isn't this should be done somewhere in drivers/clk/qcom,
Like its done for any other qcom board?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ