linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dzmitry Sankouski <dsankouski@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Sebastian Reichel <sre@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>, Lee Jones <lee@kernel.org>,
	 Rob Herring <robh@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Pavel Machek <pavel@ucw.cz>,  Hans de Goede <hdegoede@redhat.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	 Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>,
	Purism Kernel Team <kernel@puri.sm>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 devicetree@vger.kernel.org, linux-input@vger.kernel.org,
	 linux-leds@vger.kernel.org
Subject: Re: [PATCH v15 6/7] input: max77693: add max77705 haptic support
Date: Fri, 17 Jan 2025 15:32:23 +0300	[thread overview]
Message-ID: <CABTCjFBF7C=MOcLgyyQg3FeRF3gVVPASDGBT+ogCTSLs-yQo6w@mail.gmail.com> (raw)
In-Reply-To: <20250117-chubby-convivial-axolotl-29e2df@krzk-bin>

пт, 17 янв. 2025 г. в 11:01, Krzysztof Kozlowski <krzk@kernel.org>:
>
> On Thu, Jan 16, 2025 at 07:26:08PM +0300, Dzmitry Sankouski wrote:
> >  #define MAX_MAGNITUDE_SHIFT  16
> > @@ -115,6 +116,13 @@ static int max77693_haptic_configure(struct max77693_haptic *haptic,
> >                       MAX77693_HAPTIC_PWM_DIVISOR_128);
> >               config_reg = MAX77693_HAPTIC_REG_CONFIG2;
> >               break;
> > +     case TYPE_MAX77705:
> > +             value = ((haptic->type << MAX77693_CONFIG2_MODE) |
> > +                     (enable << MAX77693_CONFIG2_MEN) |
> > +                     (haptic->mode << MAX77693_CONFIG2_HTYP) |
> > +                     MAX77693_HAPTIC_PWM_DIVISOR_128);
>
> That's the same as previous one, why duplicating?
>

config_reg is different. I don't see any good way to get rid of that duplication

> > +             config_reg = MAX77705_PMIC_REG_MCONFIG;
> > +             break;
> >       case TYPE_MAX77843:
> >               value = (haptic->type << MCONFIG_MODE_SHIFT) |
> >                       (enable << MCONFIG_MEN_SHIFT) |
(...)
> >
> >  static const struct platform_device_id max77693_haptic_id[] = {
> >       { "max77693-haptic", },
> > +     { "max77705-haptic", },
> >       { "max77843-haptic", },
> >       {},
> >  };
> > @@ -414,6 +426,7 @@ MODULE_DEVICE_TABLE(platform, max77693_haptic_id);
> >
> >  static const struct of_device_id of_max77693_haptic_dt_match[] = {
> >       { .compatible = "maxim,max77693-haptic", },
> > +     { .compatible = "maxim,max77705-haptic", },
>
> So the device looks fully compatible with max77693. Drop this change and
> express compatibility with fallback.
>

The only difference is config_reg.

  parent reply	other threads:[~2025-01-17 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 16:26 [PATCH v15 0/7] Add support for Maxim Integrated MAX77705 PMIC Dzmitry Sankouski
2025-01-16 16:26 ` [PATCH v15 1/7] dt-bindings: power: supply: add maxim,max77705 charger Dzmitry Sankouski
2025-01-16 16:26 ` [PATCH v15 2/7] dt-bindings: mfd: add maxim,max77705 Dzmitry Sankouski
2025-01-16 16:26 ` [PATCH v15 3/7] power: supply: max77705: Add charger driver for Maxim 77705 Dzmitry Sankouski
2025-01-16 16:26 ` [PATCH v15 4/7] mfd: simple-mfd-i2c: Add MAX77705 support Dzmitry Sankouski
2025-01-16 16:26 ` [PATCH v15 5/7] mfd: Add new driver for MAX77705 PMIC Dzmitry Sankouski
2025-01-17  7:55   ` Krzysztof Kozlowski
2025-01-17 11:53     ` Dzmitry Sankouski
2025-01-16 16:26 ` [PATCH v15 6/7] input: max77693: add max77705 haptic support Dzmitry Sankouski
2025-01-17  8:01   ` Krzysztof Kozlowski
2025-01-17  8:02     ` Krzysztof Kozlowski
2025-01-17 12:40       ` Dzmitry Sankouski
2025-01-17 12:32     ` Dzmitry Sankouski [this message]
2025-01-16 16:26 ` [PATCH v15 7/7] leds: max77705: Add LEDs support Dzmitry Sankouski

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='CABTCjFBF7C=MOcLgyyQg3FeRF3gVVPASDGBT+ogCTSLs-yQo6w@mail.gmail.com' \
    --to=dsankouski@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=kernel@puri.sm \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=pavel@ucw.cz \
    --cc=robh@kernel.org \
    --cc=sebastian.krzyszkowiak@puri.sm \
    --cc=sre@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;
as well as URLs for NNTP newsgroup(s).