Commit 2ccb9cc3 authored by Andy Shevchenko's avatar Andy Shevchenko
Browse files

pinctrl: intel: Update description in struct intel_community 



It appears that most of the drivers, that are using struct intel_community,
utilize gpps rather than gpp_size. Update comment accordingly.

While here, correct the description of gpp_size, i.e. remove double space
and drop redundant 'etc.' part.

Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
parent 3dbf1ee6

drivers/pinctrl/intel/pinctrl-intel.h

+3 −3
Original line number Diff line number Diff line
@@ -95,7 +95,7 @@ enum { 
 * @features: Additional features supported by the hardware

 * @pin_base: Starting pin of pins in this community

 * @gpp_size: Maximum number of pads in each group, such as PADCFGLOCK,

 *            HOSTSW_OWN,  GPI_IS, GPI_IE, etc. Used when @gpps is %NULL.

 *            HOSTSW_OWN, GPI_IS, GPI_IE. Used when @gpps is %NULL.

 * @gpp_num_padown_regs: Number of pad registers each pad group consumes at

 *			 minimum. Use %0 if the number of registers can be

 *			 determined by the size of the group.
@@ -106,8 +106,8 @@ enum { 
 * @regs: Community specific common registers (reserved for core driver)

 * @pad_regs: Community specific pad registers (reserved for core driver)

 *

 * Most Intel GPIO host controllers this driver supports each pad group is

 * of equal size (except the last one). In that case the driver can just

 * In some of Intel GPIO host controllers this driver supports each pad group

 * is of equal size (except the last one). In that case the driver can just

 * fill in @gpp_size field and let the core driver to handle the rest. If

 * the controller has pad groups of variable size the client driver can

 * pass custom @gpps and @ngpps instead.