Re: [PATCH 1/1] pinctrl: Add alternative way for specifying register bases

Hi, Light I knew your idea, but the patch really depends on a separate patch about the update of the corresponding dt-binding document for your newly added properties. You can find out dt-binding document pinctrl-mt8183.txt in linux-pinctrl.git branch for-next that is just being merged two weeks a

Re: [PATCH 1/1] pinctrl: Add alternative way for specifying register bases

Hi, Sean: On Sun, 2019-04-14 at 16:01 -0700, Sean Wang wrote: > Hi, Light > > On Thu, Apr 11, 2019 at 8:15 PM Light Hsieh wrote: > > > > The orginal PINCTRL_MTK_PARIS/PINCTRL_MTK_MOORE need more effort for > > specifying register bases when porting platform driver: > > 1. Write mt_pinctrl_re

Re: [PATCH 1/1] pinctrl: Add alternative way for specifying register bases

Hi, Light On Thu, Apr 11, 2019 at 8:15 PM Light Hsieh wrote: > > The orginal PINCTRL_MTK_PARIS/PINCTRL_MTK_MOORE need more effort for > specifying register bases when porting platform driver: > 1. Write mt_pinctrl_register_base_name[] array in pinctrl-mt.c >to specify names of registe

[PATCH 1/1] pinctrl: Add alternative way for specifying register bases

The orginal PINCTRL_MTK_PARIS/PINCTRL_MTK_MOORE need more effort for specifying register bases when porting platform driver: 1. Write mt_pinctrl_register_base_name[] array in pinctrl-mt.c to specify names of register bases, for exmaple: static const char * const mt6765_pinctrl_r