Hi Simon, On Thu, 15 Dec 2011 14:41:59 +0100 Simon Budig <simon.budig@xxxxxxxxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/15/2011 01:17 PM, agust@xxxxxxx wrote: > > My understanding is that CodingStyle insists on tabs for > > indentation and tabs are always 8 characters wide. Additional > > indentation for alignment of function arguments is done by > > spaces, i.e.: > > > > <tab>function(arg1, > > <tab><tab> arg2); > > Hrm, in my perception arg2 should be on the same indentation level as > function(, since it is within the same block. > > Anyway, I'll ignore the whitespace complaints of checkpatch.pl for now. > I am then down to three warnings about >80 character lines, which are > not easy to fix. > > However, when trying my patch against the latest mainline it complains > about an implicit declaration of function irq_to_gpio(). > > I understand that irq_to_gpio() is a potentially nasty thing to do and > that there has been some cleanup. But I am unsure how to fix this: > > Currently I use the .irq field of the i2c_board_info struct to define > the irq to respond to. I expect this to be a gpio irq and hence use > irq_to_gpio to configure the resp. gpio as input. > > If I am not supposed to use irq_to_gpio, then how do I solve this? > > * expect the board file to set up the resp. GPIO direction? That would mean that each board using the driver have to add this code. I'd prefer to do it in the driver itself to reduce code duplication. > or > > * use an entry in my platform data (next to the reset pin) for the gpio > number and then try to map this to an irq number? Since we already have platform data and can't get rid of it now, adding gpio entry and mapping to irq would be better. > or did I miss the best solution? In the long term switching to device tree configuration would be the right way to go, I think. But for now we have to wait until arch/platform code is converted to device tree usage. Thanks, Anatoij -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
