mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Brugger <mbrugger@suse.com>
To: Gene Chen <gene.chen.richtek@gmail.com>, matthias.bgg@kernel.org
Cc: Lee Jones <lee.jones@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Gene Chen <gene_chen@richtek.com>,
	"moderated list:ARM/Mediatek SoC support" 
	<linux-mediatek@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
	ChiYuan Huang <cy_huang@richtek.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH] mfd: mt6360: Fix MFD cell names and compatibles
Date: Mon, 11 Jan 2021 15:38:57 +0100	[thread overview]
Message-ID: <392f08b4-0e46-3ba3-2515-640a05accbcb@suse.com> (raw)
In-Reply-To: <CAE+NS35Br8jgLfii=VPjFx+m+9=a=EQKYyoQMAyd7Zdo0K6n+A@mail.gmail.com>



On 11/01/2021 14:05, Gene Chen wrote:
> Hi Lee,
> 
> This change exists in [PATCH v7 03/11] mfd: mt6360: Indicate sub-dev
> compatible name by using "-".
> Does patch v7 also merge together to mfd-next?
> 

once again, please don't top-post.

Sorry I didn't saw this patch. Looks good to me, so please ignore this patch mine.

Regards,
Matthias

> <matthias.bgg@kernel.org> 於 2021年1月11日 週一 下午8:35寫道:
>>
>> From: Matthias Brugger <mbrugger@suse.com>
>>
>> MFD cell names and compatibles use '_' instead of '-', which is common
>> practice for names and the standard for DT compatibles.
>> This will also fix the probing for the drivers already implemented
>> (mt6360-adc and mt6360-tcpc).
>>
>> Fixes: 7edd363421da ("mfd: Add support for PMIC MT6360")
>> Fixes: 1f4877218f7e ("iio: adc: mt6360: Add ADC driver for MT6360")
>> Fixes: e1aefcdd394f ("usb typec: mt6360: Add support for mt6360 Type-C driver")
>> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
>>
>> ---
>>
>>  drivers/mfd/mt6360-core.c | 24 ++++++++++++------------
>>  1 file changed, 12 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/mfd/mt6360-core.c b/drivers/mfd/mt6360-core.c
>> index 4661c1b29a72..14e649ffe50f 100644
>> --- a/drivers/mfd/mt6360-core.c
>> +++ b/drivers/mfd/mt6360-core.c
>> @@ -292,18 +292,18 @@ static const struct resource mt6360_ldo_resources[] = {
>>  };
>>
>>  static const struct mfd_cell mt6360_devs[] = {
>> -       OF_MFD_CELL("mt6360_adc", mt6360_adc_resources,
>> -                   NULL, 0, 0, "mediatek,mt6360_adc"),
>> -       OF_MFD_CELL("mt6360_chg", mt6360_chg_resources,
>> -                   NULL, 0, 0, "mediatek,mt6360_chg"),
>> -       OF_MFD_CELL("mt6360_led", mt6360_led_resources,
>> -                   NULL, 0, 0, "mediatek,mt6360_led"),
>> -       OF_MFD_CELL("mt6360_pmic", mt6360_pmic_resources,
>> -                   NULL, 0, 0, "mediatek,mt6360_pmic"),
>> -       OF_MFD_CELL("mt6360_ldo", mt6360_ldo_resources,
>> -                   NULL, 0, 0, "mediatek,mt6360_ldo"),
>> -       OF_MFD_CELL("mt6360_tcpc", NULL,
>> -                   NULL, 0, 0, "mediatek,mt6360_tcpc"),
>> +       OF_MFD_CELL("mt6360-adc", mt6360_adc_resources,
>> +                   NULL, 0, 0, "mediatek,mt6360-adc"),
>> +       OF_MFD_CELL("mt6360-chg", mt6360_chg_resources,
>> +                   NULL, 0, 0, "mediatek,mt6360-chg"),
>> +       OF_MFD_CELL("mt6360-led", mt6360_led_resources,
>> +                   NULL, 0, 0, "mediatek,mt6360-led"),
>> +       OF_MFD_CELL("mt6360-pmic", mt6360_pmic_resources,
>> +                   NULL, 0, 0, "mediatek,mt6360-pmic"),
>> +       OF_MFD_CELL("mt6360-ldo", mt6360_ldo_resources,
>> +                   NULL, 0, 0, "mediatek,mt6360-ldo"),
>> +       OF_MFD_CELL("mt6360-tcpc", NULL,
>> +                   NULL, 0, 0, "mediatek,mt6360-tcpc"),
>>  };
>>
>>  static const unsigned short mt6360_slave_addr[MT6360_SLAVE_MAX] = {
>> --
>> 2.29.2
>>
> 


      reply	other threads:[~2021-01-11 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 12:35 matthias.bgg
2021-01-11 13:05 ` Gene Chen
2021-01-11 14:38   ` Matthias Brugger [this message]

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=392f08b4-0e46-3ba3-2515-640a05accbcb@suse.com \
    --to=mbrugger@suse.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=cy_huang@richtek.com \
    --cc=gene.chen.richtek@gmail.com \
    --cc=gene_chen@richtek.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=matthias.bgg@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

all inboxes | Powered by JetHome®