On Fri, 2013-10-04 at 17:27 +0200, Michal Simek wrote: > Hi, > > On 10/03/2013 11:46 PM, Alan Tull wrote: > > On Wed, 2013-10-02 at 17:35 +0200, Michal Simek wrote: > > > >> > >> Through firmware interface: > >> cat /sys/class/fpga_manager/fpga0/name > >> echo -n fpga.bin > /sys/class/fpga_manager/fpga0/firmware > >> > >> Through sysfs bin file: > >> cat /sys/class/fpga_manager/fpga0/fpga_config_state > >> echo -n write_init > /sys/class/fpga_manager/fpga0/fpga_config_state > >> cat /lib/firmware/fpga.bin > /sys/class/fpga_manager/fpga0/fpga_config_data > >> echo -n write_complete > /sys/class/fpga_manager/fpga0/fpga_config_state > >> > > > > Hi Michal, > > > > I have v2 working for me with Altera socfpga and had some feedback. > > > > Add me and Dinh as maintainers. > > why not just one? What about you? That's fine. Just add "Alan Tull <atull@xxxxxxxxxx>" So we can expect that in v3, right? > > > > This driver now has two interfaces for programming the image. > > I don't think things in the kernel usually have multiple interfaces. > > The question here is if this is a problem. i2c create char devices > and also provide sysfs access too. It is done through notification. i2c_master_send() is called as the fops write or from an i2c client, but not by writing data to some attribute under sysfs. So there aren't two direct paths from userspace to the i2c core. I am advocating against multiple ways for userspace to request/send fpga images for programming. > > > Does the fpga community in general find that the firmware class is > > suitable for all our use cases? I think it only supports the most simple > > use cases. > > Let's continue with this on that second thread and we will see what happen. Yes, let's continue this particular discussion on the other thread. > > > > My original fpga framework that you started with supported writing the > > fpga device through the devnode, i.e. > > cat fpga.bin > /dev/fpga0 > > I think we should get back to that basic char driver interface like that. > > It seems like if you have a char driver, you would open and write to the > > devnode instead of adding an attribute under /sys. > > It is the same as above. As you know we can simple add support for char > device with the current set of functions without changing logic in the driver. > > > > > The 'flags' implementation is a nice way to do some locking. But it doesn't > > replace the status op to get fpga manager status which vanished in v2. > > So please add that back. Its interface was that catting the 'status' > > attribute got a status description from the low level driver such as > > 'power up phase' or 'reset phase'. Too useful to just get rid of. > > No problem to add it back but it means that core will loose control > about values which can be returned back to the user. It is probably better > to create set of return values. > > Thanks, > Michal > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
