RFC: can we get rid of ->request_port() boilerplate ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi folks,


we've got lots of cases, where ->request_port() / ->release_port()
are just (request|release)_mem_region calls, where the parameter
values are practicall known after the device is initialized (*1).
The only preparation needed for that is changing the individual
drivers to initialize mapsize field on probing (*2).

I see two practical options for that:

a) introduce generic helpers, which are assigned as driver callbacks
   instead of the currently used driver specific ones.

b) introduce a flag which tells the serial core to do that.


What's your oppinion on that ?

If you like, I can prepare some patches and post them here.


--mtx

*1) this also can be done w/ 8250, even though currently an extra
function is called to compute the io size - I've already sent a
patch for that some time ago.
*2) already sent patches for that, a while go.

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@xxxxxxxxx -- +49-151-27565287



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux