From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Jones Subject: Re: [PATCH 1/5] drivers: input: keyboard: st-keyscan: add keyscan driver Date: Fri, 14 Mar 2014 10:42:22 +0000 Message-ID: <20140314104222.GB3432@lee--X1> References: <1393990772-9567-1-git-send-email-gabriel.fernandez@st.com> <1393990772-9567-2-git-send-email-gabriel.fernandez@st.com> <20140310114819.GO14976@lee--X1> <5322D63D.5030403@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <5322D63D.5030403@st.com> Sender: linux-input-owner@vger.kernel.org To: Gabriel Fernandez Cc: Dmitry Torokhov , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Rob Landley , Russell King , Grant Likely , devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org, kernel@stlinux.com, Giuseppe Condorelli List-Id: devicetree@vger.kernel.org > >Sorry for the delay. It was a hectic week last week. > > > >As promised: > > > >>This patch adds ST Keyscan driver to use the keypad hw a subset > >>of ST boards provide. Specific board setup will be put in the > >>given dt. > >> > >>Signed-off-by: Giuseppe Condorelli > >>Signed-off-by: Gabriel Fernandez > >Are you sure these are in the correct order? > ok i change the order I'm not saying they are in the wrong order, I'm just asking. Who wrote the patch? Has it changed since? > >>+- linux,keymap: The keymap for keys as described in the binding do= cument > >>+ devicetree/bindings/input/matrix-keymap.txt. > >>+ > >>+- keypad,num-rows: Number of row lines connected to the keypad con= troller. > >>+ > >>+- keypad,num-columns: Number of column lines connected to the keyp= ad > >>+ controller. > >>+ > >>+- st,debounce_us: Debouncing interval time in microseconds > >I'm sure there will be a shared binding for de-bounce. > > > >If not, there certainly should be. >=20 > you want to refer to "debounce-interval" ? That sounds more generic, but if it's not documented as such, then please consider doing so. > >+Example: > >+ > >+keyscan: keyscan@fe4b0000 { > >+ compatible =3D "st,keypad"; > >Is there any way we can make this more specific to _this_ IP? > for my knowledge this IP is the same for stixxxx platform. So st,stix-keypad, or st,sti4x-keypad? I'm just thinking about future proofing the architecture. What if ST released stj which has a different keypad IP? > >>+struct keyscan_priv { > >>+ void __iomem *base; > >>+ int irq; > >>+ struct clk *clk; > >>+ struct input_dev *input_dev; > >>+ struct keypad_platform_data *config; > >>+ unsigned int last_state; > >>+ u32 keycodes[ST_KEYSCAN_MAXKEYS]; > >Seems odd to limit this. Can't the information come from DT > >i.e. keypad,num-rows and keypad,num-columns? > > > i 'll rename 'num_out_pads' into 'n_rows' and 'num_in_pads' into > 'n_cols' That's not quite what I meant, I mean can't ST_KEY_MAXKEYS be more dynamic and be obtained from (keypad,num-rows * keypad,num-columns)? --=20 Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org =E2=94=82 Open source software for ARM SoCs =46ollow Linaro: Facebook | Twitter | Blog -- 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