Re: Is most drivers interfaces should be driver or application specific?
Ok, thanks. But I saw it seems I/O manager is merely a wrapper to open / close / read / write function pointer? On Fri, Sep 16, 2022 at 8:13 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14.09.22 11:55, Y. HB wrote: > > Hello all. > > > > I'm writing drivers ( like ADC ) for tms570 on RTEMS. > > To my understanding for now, there are two ways to implement non common > > interface drivers. > > 1. write a specific driver.h/.c pair to be called like PWM driver inside > > bsps/arm/beagle/ > > 2. use I/O Manager interfaces. > > > > The latter IO Manager way still requires a specific void * argument to > > pass actual parameters into the driver, but at least it could provide a > > way to make application specific or general driver interface not SoC / > > Device specific. > > > > Is my understanding correct? > > I would not use the IO Manager for new drivers. It would introduced > overheads and leads to difficult to use interfaces (ioctl). > > -- > embedded brains GmbH > Herr Sebastian HUBER > Dornierstr. 4 > 82178 Puchheim > Germany > email: sebastian.hu...@embedded-brains.de > phone: +49-89-18 94 741 - 16 > fax: +49-89-18 94 741 - 08 > > Registergericht: Amtsgericht München > Registernummer: HRB 157899 > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler > Unsere Datenschutzerklärung finden Sie hier: > https://embedded-brains.de/datenschutzerklaerung/ > ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
Re: Is most drivers interfaces should be driver or application specific?
On 14.09.22 11:55, Y. HB wrote: Hello all. I'm writing drivers ( like ADC ) for tms570 on RTEMS. To my understanding for now, there are two ways to implement non common interface drivers. 1. write a specific driver.h/.c pair to be called like PWM driver inside bsps/arm/beagle/ 2. use I/O Manager interfaces. The latter IO Manager way still requires a specific void * argument to pass actual parameters into the driver, but at least it could provide a way to make application specific or general driver interface not SoC / Device specific. Is my understanding correct? I would not use the IO Manager for new drivers. It would introduced overheads and leads to difficult to use interfaces (ioctl). -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
Is most drivers interfaces should be driver or application specific?
Hello all. I'm writing drivers ( like ADC ) for tms570 on RTEMS. To my understanding for now, there are two ways to implement non common interface drivers. 1. write a specific driver.h/.c pair to be called like PWM driver inside bsps/arm/beagle/ 2. use I/O Manager interfaces. The latter IO Manager way still requires a specific void * argument to pass actual parameters into the driver, but at least it could provide a way to make application specific or general driver interface not SoC / Device specific. Is my understanding correct? ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
