linux-kernel - Re: [PATCH v2 1/5] misc: sensorhub: Add sensorhub driver

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, 24 Nov 2014 14:04:48 +0100
From:	Karol Wrona <k.wrona@...sung.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Jonathan Cameron <jic23@...nel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Lee Jones <lee.jones@...aro.org>, linux-iio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCH v2 1/5] misc: sensorhub: Add sensorhub driver

On 11/24/2014 01:35 PM, Arnd Bergmann wrote:
> On Monday 24 November 2014 12:39:12 Karol Wrona wrote:
>> It is possible that it can serve as input device sth else. So you are
>> right about MFD.
>>
>> The structure of mfd directory is flat. I wonder what can be better:
>> just putting these sources inside mfd dir or to some new category inside mfd.
>> Generally sensorhub will not differ than others mfd devs but in the near future
>> it can be that we end up with different (sensor)hubs or in my case with one core
>> driver with several interfaces, mcu's modes - sth like ssp-i2c.c etc.
>> These drivers can grow in size as these devices will appear in different boards.
>
> You should be able to abstract the interface differences using regmap for the
> most part, so there would only be a small stub that is i2c or spi specific,
> and a lot of mfd drivers have that.
>
>> Also there is a question where firmware loader (stm32fwu) should be placed as it
>> is a library?
>
> Can you describe what this library does? Is this for loading firmware into
> device RAM or into flash? Does it always use USB?
Generally it uploads firmware to STM32F4xx mcu using SPI. Now it writes to 
flash. Its is a subset of STM32 boot code protocol (I suppose version 1.0 but it 
is poorly documented, version 1.1 is available on ST site) so it always can be 
improved to support full protocol or other interfaces.

>
> 	Arnd
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/