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: <CAHp75VejaaBPvO3qBxwBTDR9bq_nr0bT7uSKi66tnA=_S96W5Q@mail.gmail.com>
Date:   Mon, 15 May 2017 16:35:05 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Dong Aisheng <aisheng.dong@....com>
Cc:     "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.com>, fugang.duan@....com,
        Stefan Agner <stefan@...er.ch>, dongas86@...il.com,
        Mingkai.Hu@....com, yangbo.lu@....com
Subject: Re: [PATCH V2 1/6] tty: serial: lpuart: introduce lpuart_soc_data to
 represent SoC property

On Mon, May 15, 2017 at 10:48 AM, Dong Aisheng <aisheng.dong@....com> wrote:
> This is used to dynamically check the SoC specific lpuart properies.
> Currently only the checking of 32 bit register width is added which
> functions the same as before. More will be added later for supporting
> new chips.

For the rest it might be okay, but don't we have specific properties
for register width and offset for UART? I think I saw something like
that in other drivers.

-- 
With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ