[PATCH linux v4 20/20] drivers/fsi: Add SCOM client driver
Christopher Bostic
christopher.lee.bostic at gmail.com
Tue Oct 18 02:10:20 AEDT 2016
On Mon, Oct 17, 2016 at 2:27 AM, Jeremy Kerr <jk at ozlabs.org> wrote:
> Hi Chris,
>
>> + /* todo: fill in and register cdev */
>> + /* open, read, write, close file ops */
>> +
>> + /* todo: user space linkage to get_scom / put_scom */
>> + /* engine init */
>
> We have a couple of options for this, but I think a simple chardev would
> work fine. Were you thinking just a read/write interface, where the
> off_t is the SCOM address?
>
Hi Jeremy,
Yes, the idea was to create the char dev and use the read/write syscalls.
Might be a good topic for discussion in tonight's call. Want to make sure
this adheres to the general openBMC plan for user space access to
the kernel.
Thanks,
-Chris
> Cheers,
>
>
> Jeremy
More information about the openbmc
mailing list