All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Dmitry Torokhov' <dmitry.torokhov@gmail.com>,
	linux-samsung-soc@vger.kernel.org, kyungmin.park@samsung.com,
	ben-linux@fluff.org, linux-input@vger.kernel.org,
	ch.naveen@samsung.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/3] input: samsung-keypad - Add samsung keypad driver
Date: Mon, 02 Aug 2010 12:09:16 +0900	[thread overview]
Message-ID: <4C5636DC.5070703@samsung.com> (raw)
In-Reply-To: <009501cb28d1$c54c9f00$4fe5dd00$%kim@samsung.com>

Hi, I came back from vacation.

>>>> Do you have any feedback? If ok, i want to go to input tree or samsung
>>>> tree these added sched.h including.
>>> I applied the patch adding samsung-keypad.c and the platform data
>>> arch/arm/plat-samsung/include/plat/keypad.h and I expect that
>>> patches to actually enable keypad will go through appropriate
>>> platform tree(s).
>>>
>> OK, the rest will go through samsung platform tree
>>
> Ok..will apply.
> 

Kukjin, could you remove keypad.h on the commit "ARM: SAMSUNG: Add 
keypad device support" of the samsung platform tree. The keypad.h file
was included on input tree.
(http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=0fffed27f92d9d7a34de9fe017b7082b5958bb93)

>>> The only caveat is that I removed declarations for copying platform data
>>> around and for gpio config function - if it is there there is no point
>>> of invoking it through the pointer in platform data.
>>>
>> I agree, but currently samsung platform framework uses such this way. I
>> believe these can change later at once.
>>

Dmitry, could you apply original keypad.h. We can get problem such this
on most samsung device driver too. As i said before, these can be fixed
later.

>>> Overall I am confused why you set up keypad in platform code in the
>>> way you do. I'd put the device definitions and all supporting functions
>>> in the same module that registers platform device and be done with it.
>>>
>> Thanks.
> 
> 
> Thanks.
> 
> Best regards,
> Kgene.
> --
> Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
> SW Solution Development Team, Samsung Electronics Co., Ltd.
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

WARNING: multiple messages have this Message-ID (diff)
From: jy0922.shim@samsung.com (Joonyoung Shim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/3] input: samsung-keypad - Add samsung keypad driver
Date: Mon, 02 Aug 2010 12:09:16 +0900	[thread overview]
Message-ID: <4C5636DC.5070703@samsung.com> (raw)
In-Reply-To: <009501cb28d1$c54c9f00$4fe5dd00$%kim@samsung.com>

Hi, I came back from vacation.

>>>> Do you have any feedback? If ok, i want to go to input tree or samsung
>>>> tree these added sched.h including.
>>> I applied the patch adding samsung-keypad.c and the platform data
>>> arch/arm/plat-samsung/include/plat/keypad.h and I expect that
>>> patches to actually enable keypad will go through appropriate
>>> platform tree(s).
>>>
>> OK, the rest will go through samsung platform tree
>>
> Ok..will apply.
> 

Kukjin, could you remove keypad.h on the commit "ARM: SAMSUNG: Add 
keypad device support" of the samsung platform tree. The keypad.h file
was included on input tree.
(http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=0fffed27f92d9d7a34de9fe017b7082b5958bb93)

>>> The only caveat is that I removed declarations for copying platform data
>>> around and for gpio config function - if it is there there is no point
>>> of invoking it through the pointer in platform data.
>>>
>> I agree, but currently samsung platform framework uses such this way. I
>> believe these can change later at once.
>>

Dmitry, could you apply original keypad.h. We can get problem such this
on most samsung device driver too. As i said before, these can be fixed
later.

>>> Overall I am confused why you set up keypad in platform code in the
>>> way you do. I'd put the device definitions and all supporting functions
>>> in the same module that registers platform device and be done with it.
>>>
>> Thanks.
> 
> 
> Thanks.
> 
> Best regards,
> Kgene.
> --
> Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
> SW Solution Development Team, Samsung Electronics Co., Ltd.
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  reply	other threads:[~2010-08-02  3:09 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 11:33 [PATCH v6 1/3] ARM: SAMSUNG: Add keypad device support Joonyoung Shim
2010-06-28 11:33 ` Joonyoung Shim
2010-06-28 11:33 ` [PATCH v6 2/3] ARM: S5PV210: Add keypad device helpers Joonyoung Shim
2010-06-28 11:33   ` Joonyoung Shim
2010-06-28 11:33 ` [PATCH v6 3/3] input: samsung-keypad - Add samsung keypad driver Joonyoung Shim
2010-06-28 11:33   ` Joonyoung Shim
2010-07-06  7:58   ` Joonyoung Shim
2010-07-06  7:58     ` Joonyoung Shim
2010-07-06 23:52     ` Kukjin Kim
2010-07-06 23:52       ` Kukjin Kim
2010-07-07  1:28       ` Joonyoung Shim
2010-07-07  1:28         ` Joonyoung Shim
2010-07-09  7:07         ` Kukjin Kim
2010-07-09  7:07           ` Kukjin Kim
2010-07-09  7:39           ` Joonyoung Shim
2010-07-09  7:39             ` Joonyoung Shim
2010-07-21  5:42             ` Joonyoung Shim
2010-07-21  5:42               ` Joonyoung Shim
2010-07-21  6:21               ` Kukjin Kim
2010-07-21  6:21                 ` Kukjin Kim
2010-07-21  8:07               ` Dmitry Torokhov
2010-07-21  8:07                 ` Dmitry Torokhov
2010-07-21  9:01                 ` Joonyoung Shim
2010-07-21  9:01                   ` Joonyoung Shim
2010-07-21 12:39                   ` Kukjin Kim
2010-07-21 12:39                     ` Kukjin Kim
2010-08-02  3:09                     ` Joonyoung Shim [this message]
2010-08-02  3:09                       ` Joonyoung Shim
2010-08-02  3:38                       ` Kukjin Kim
2010-08-02  3:38                         ` Kukjin Kim
2010-08-02  4:41                         ` Joonyoung Shim
2010-08-02  4:41                           ` Joonyoung Shim
2010-08-02  5:12                           ` Kukjin Kim
2010-08-02  5:12                             ` Kukjin Kim
2010-08-02  5:52                             ` Joonyoung Shim
2010-08-02  5:52                               ` Joonyoung Shim
2010-08-02  6:30                               ` Kukjin Kim
2010-08-02  6:30                                 ` Kukjin Kim
2010-08-02  7:58                                 ` Dmitry Torokhov
2010-08-02  7:58                                   ` Dmitry Torokhov
2010-08-03  2:10                                   ` Kukjin Kim
2010-08-03  2:10                                     ` Kukjin Kim

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=4C5636DC.5070703@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=ch.naveen@samsung.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-samsung-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.