linux-kernel - Re: [PATCH] mfd: Add driver for RAVE Supervisory Processor

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]

Date:   Mon, 12 Jun 2017 17:28:09 -0700
From:   Andrey Smirnov <andrew.smirnov@...il.com>
To:     Lucas Stach <l.stach@...gutronix.de>
Cc:     Lee Jones <lee.jones@...aro.org>, Chris Healy <cphealy@...il.com>,
        Nikita Yushchenko <nikita.yoush@...entembedded.com>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        devicetree@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mfd: Add driver for RAVE Supervisory Processor

On Wed, Jun 7, 2017 at 1:41 AM, Lucas Stach <l.stach@...gutronix.de> wrote:
> Hi Andrey,
>
> no code review, just 2 drive-by comments.
>
> Am Dienstag, den 06.06.2017, 11:06 -0700 schrieb Andrey Smirnov:
>> Add a driver for RAVE Supervisory Processor, an MCU implementing
>> varoius bits of housekeeping functionality (watchdoging, backlight
>> control, LED control, etc) on RAVE family of products by Zodiac
>> Inflight Innovations.
>>
>> This driver implementes core MFD/serdev device as well as
>> communication subroutines necessary for commanding the device.
>>
>> Cc: cphealy@...il.com
>> Cc: Lucas Stach <l.stach@...gutronix.de>
>> Cc: Nikita Yushchenko <nikita.yoush@...entembedded.com>
>> Cc: Rob Herring <robh+dt@...nel.org>
>> Cc: Mark Rutland <mark.rutland@....com>
>> Cc: devicetree@...r.kernel.org
>> Cc: linux-kernel@...r.kernel.org
>> Signed-off-by: Andrey Smirnov <andrew.smirnov@...il.com>
>> ---
> [...]
>
>> +++ b/drivers/mfd/rave-sp.c
>> @@ -0,0 +1,1009 @@
>> +/*
>> + * rave-sp.c - Multifunction core driver for Zodiac Inflight Innovations
>> + * SP MCU that is connected via dedicated UART port
>> + *
>> + * Copyright (C) 2017 Zodiac Inflight Innovations
>> + *
>> + * This program is free software; you can redistribute it and/or
>> + * modify it under the terms of the GNU General Public License as
>> + * published by the Free Software Foundation; either version 2 of
>> + * the License, or (at your option) any later version.
>> + *
>> + * This program is distributed in the hope that it will be useful,
>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>> + * GNU General Public License for more details.
>> + *
>> + * You should have received a copy of the GNU General Public License
>> + * along with this program; if not, see <http://www.gnu.org/licenses/>.
>> + */
>
> [...]
>
>> +MODULE_DEVICE_TABLE(of, rave_sp_dt_ids);
>> +MODULE_LICENSE("GPL");
>
> Header says GPL v2, so this should be changed to match.
>

OK, will fix in v2.

> [...]
>> +
>> +#define COMPATIBLE_RAVE_SP_NIU               "zii,rave-sp-niu"
>> +#define COMPATIBLE_RAVE_SP_MEZZ              "zii,rave-sp-mezz"
>> +#define COMPATIBLE_RAVE_SP_ESB               "zii,rave-sp-esb"
>> +#define COMPATIBLE_RAVE_SP_RDU1              "zii,rave-sp-rdu1"
>> +#define COMPATIBLE_RAVE_SP_RDU2              "zii,rave-sp-rdu2"
>
> Can we get rid of those defines? They are only used in the of_device_id
> table.

Those defines are used by drivers for MFD cells, because,
unfortunately, communication protocols differ for between hardware
versions. So instead of having, say, "zii,rave-sp-watchdog-rdu2",
"zii,rave-sp-watchdog-rdu1", etc. I use "zii,rave-sp-watchdog" and
"compatible" from MFD parent to determine what protocol to use. I am
happy to change that if that doesn't seem like a good idea.

Thanks,
Andrey Smirnov