linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Tatsunosuke Tobita <junkpainting@gmail.com>
Cc: linux-input@vger.kernel.org, dtor@mail.ru
Subject: Re: [PATCH] Input: Add a driver to support for Wacom I2C Stylus Device
Date: Tue, 20 Dec 2011 15:36:57 +0800	[thread overview]
Message-ID: <4EF03B19.2020208@cn.fujitsu.com> (raw)
In-Reply-To: <CA+MtpR27gCd9fCPZT_C9nZhFkDrEVNuhc9W=5vzAe5r2+feuJQ@mail.gmail.com>

On 12/20/2011 02:32 PM, Tatsunosuke Tobita wrote:

> Hi Wanlong,
> 
> Thank you for your review.
> But, I'm not sure about driver-core-next; is this in linux-input somewhere?
> or should I update my git branch ?


No, it means Greg's driver-core tree. He queued the changes to next, and will
be merged to linus' tree through next merge window, and input-next is the same, too.

You can do like this:
git remote add driver-core git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
git remote update
git checkout -b driver-core-next driver-core/driver-core-next

Then you can see these module_*_driver changes in this branch,
but, you are doing input drivers, so, you must cook patches against Dmitry's input-next tree,
not Greg's driver-core-next branch.

I hope you can understand what I'm trying to say.

> 
> Also, I'm checking with your commit which was made yesterday and
> it looks like  "module_i2c_driver" converges both init and exit into
> one statement;
> is my understanding correct?


Yeah, you are right.

> 
> If my questions above are clear, I'll be able to correctly rewrite the code.


IMO, please do.

But, Dmitry, what do you think?


Thanks
-Wanlong Gao

> So, please help to answer.
> 
> Thanks,
> 
> Tats
> 
> On Tue, Dec 20, 2011 at 3:05 PM, Wanlong Gao <gaowanlong@cn.fujitsu.com> wrote:
>> On 12/20/2011 01:46 PM, Tatsunosuke Tobita wrote:
>>
>>> From: Tatsunosuke Tobita <tobita.tatsunosuke@wacom.co.jp>
>>>
>>> This driver supports for Wacom Stylus Device with I2C interface.
>>>
>>> Signed-off-by: Tatsunosuke Tobita <tobita.tatsunosuke@wacom.co.jp>
>>> ---
>>>  drivers/input/touchscreen/wacom_i2c.c |  250 +++++++++++++++++++++++++++++++++
>>>  drivers/input/touchscreen/wacom_i2c.h |   55 +++++++
>>>  2 files changed, 305 insertions(+), 0 deletions(-)
>>>  create mode 100644 drivers/input/touchscreen/wacom_i2c.c
>>>  create mode 100644 drivers/input/touchscreen/wacom_i2c.h
>>>
>>> diff --git a/drivers/input/touchscreen/wacom_i2c.c b/drivers/input/touchscreen/wacom_i2c.c
>>> new file mode 100644
>>> index 0000000..157bcc5
>>> --- /dev/null
>>> +++ b/drivers/input/touchscreen/wacom_i2c.c
>>
>>> +
>>> +static struct i2c_driver wacom_i2c_driver = {
>>> +     .driver = {
>>> +             .name = "wacom_i2c",
>>> +             .owner = THIS_MODULE,
>>> +             .pm = &wacom_i2c_pm,
>>> +     },
>>> +
>>> +     .probe = wacom_i2c_probe,
>>> +     .remove = __devexit_p(wacom_i2c_remove),
>>> +     .id_table = wacom_i2c_id,
>>> +};
>>> +
>>> +static int __init wacom_i2c_init(void)
>>> +{
>>> +     return i2c_add_driver(&wacom_i2c_driver);
>>> +}
>>> +
>>> +static void __exit wacom_i2c_exit(void)
>>> +{
>>> +     i2c_del_driver(&wacom_i2c_driver);
>>> +}
>>> +
>>> +module_init(wacom_i2c_init);
>>> +module_exit(wacom_i2c_exit);
>>
>>
>> You can use module_i2c_driver(wacom_i2c_driver) instead of module_init{exit},
>> it has been queued to driver-core-next already.
>>
>>
>> Thanks
>> -Wanlong Gao
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



  reply	other threads:[~2011-12-20  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20  5:46 [PATCH] Input: Add a driver to support for Wacom I2C Stylus Device Tatsunosuke Tobita
2011-12-20  6:05 ` Wanlong Gao
2011-12-20  6:32   ` Tatsunosuke Tobita
2011-12-20  7:36     ` Wanlong Gao [this message]
2011-12-20 14:28       ` Tatsunosuke Tobita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EF03B19.2020208@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=dtor@mail.ru \
    --cc=junkpainting@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).