From patchwork Wed Feb 13 13:43:24 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bartosz Golaszewski X-Patchwork-Id: 10809945 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 16DBB139A for ; Wed, 13 Feb 2019 13:45:42 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 0339D2D035 for ; Wed, 13 Feb 2019 13:45:42 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id EAC092D04A; Wed, 13 Feb 2019 13:45:41 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 43FAC2CFA6 for ; Wed, 13 Feb 2019 13:45:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390760AbfBMNnv (ORCPT ); Wed, 13 Feb 2019 08:43:51 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:56267 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390371AbfBMNnv (ORCPT ); Wed, 13 Feb 2019 08:43:51 -0500 Received: by mail-wm1-f68.google.com with SMTP id r17so2478469wmh.5 for ; Wed, 13 Feb 2019 05:43:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=DaKGiwoFvSo+r2Tcx9x2APU9LI/OjjWmyN0jSQl+CIg=; b=GRyrl2PcLq3bEEW4NKY65QOMwApyZQ5LQB41c1oPwIQ3Cj01jwmL1PTsARBvL34A5Q a/4IXainN35Vb8WEgyHtQGIgzEjXnTSliShz/V9vrhy28Lg0NFpflpglrD1EBF2zGgOL IriPAHcKb1j8s0wfoKRn1ymdLDMqmpwUvMjcxuhyluyuyd9+9NrBrqDzFM0Pepun20YN SCL0YvFhpbsXi02uQ3PDR4SUsKh76Q7xXUp+pvmzSuD10j+7AXGSlD0IFpFFKpd/8YjC Di7jLfg7nDaJmSikTD9m0bG1iEUkWB04AyDwmWG4NiRmQkdtyfZTr+G3cfl7ele7MW+C TXsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=DaKGiwoFvSo+r2Tcx9x2APU9LI/OjjWmyN0jSQl+CIg=; b=J/upjpwPwDjFTXB+cXChcZENkL3CHZitKrsCelKKVBwUtXeAZochQ4zE5JYkUHt+zP WlAkfvf3MuZ5v/EqqHrwHUmGhoDr6SulFjdsCIBVnEWEXLaZQfcFTnGmF/fE3kQcdqBT fHnmclbnEkvwISieGmp3tskdaqi9QrmwqIcly/9tY2XQ49Fh3hhPkKyqY35qW5T0pj2e 55Klii56ShZ3RrzBXh9fwR8V7G1OAOk2Xql16ea0VbWMtSrMCrGUCqzEnqvjYzfUyKF6 F9d2o0LjtaNYH3A034QMk6/bFCaSw84T++sArgQsJA+BN31/qwyuQjih+Jg2tEclPTsC 8XGg== X-Gm-Message-State: AHQUAuYi/rBEeo1QEsewirHNPL4Vahr2dPIDIxcYtlzWmCYZStI/QOoy s5J5k3lbLAM8rxgFKf7/SUVE5g== X-Google-Smtp-Source: AHgI3IZ6+WBGvks6qWHZ/K7B+9IWfkQ/q+W9zTgTcAWT9Fm5PZOJLWX5JcBkW1b3xMfs6awoFuT2dQ== X-Received: by 2002:a1c:2d08:: with SMTP id t8mr399325wmt.5.1550065428904; Wed, 13 Feb 2019 05:43:48 -0800 (PST) Received: from debian-brgl.home (amontpellier-652-1-54-116.w109-210.abo.wanadoo.fr. [109.210.45.116]) by smtp.gmail.com with ESMTPSA id e7sm2046720wrw.35.2019.02.13.05.43.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 05:43:48 -0800 (PST) From: Bartosz Golaszewski To: Rob Herring , Mark Rutland , Linus Walleij , Dmitry Torokhov , Jacek Anaszewski , Pavel Machek , Lee Jones , Sebastian Reichel , Liam Girdwood , Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-input@vger.kernel.org, linux-leds@vger.kernel.org, linux-pm@vger.kernel.org, Bartosz Golaszewski Subject: [PATCH v5 00/11] mfd: add support for max77650 PMIC Date: Wed, 13 Feb 2019 14:43:24 +0100 Message-Id: <20190213134335.10838-1-brgl@bgdev.pl> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Sender: linux-input-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP From: Bartosz Golaszewski This series adds support for max77650 ultra low-power PMIC. It provides the core mfd driver and a set of five sub-drivers for the regulator, power supply, gpio, leds and input subsystems. Patches 1-4 add the DT binding documents. Patch 5 documents mfd_add_devices(). Patches 6-10 add all drivers. Last patch adds a MAINTAINERS entry for this device. The regulator part has already been picked up into the regulator tree. v1 -> v2: ========= General: - use C++ style comments for the SPDX license identifier and the copyright header - s/MODULE_LICENSE("GPL")/MODULE_LICENSE("GPL v2")/ - lookup the virtual interrupt numbers in the MFD driver, setup resources for child devices and use platform_get_irq_byname() in sub-drivers - picked up review tags - use devm_request_any_context_irq() for interrupt requests LEDs: - changed the max77650_leds_ prefix to max77650_led_ - drop the max77650_leds structure as the only field it held was the regmap pointer, move said pointer to struct max77650_led - change the driver name to "max77650-led" - drop the last return value check and return the result of regmap_write() directly - change the labeling scheme to one consistent with other LED drivers ONKEY: - drop the key reporting helper and call the input functions directly from interrupt handlers - rename the rv local variable to error - drop parent device asignment Regulator: - drop the unnecessary init_data lookup from the driver code - drop unnecessary include Charger: - disable the charger on driver remove - change the power supply type to POWER_SUPPLY_TYPE_USB GPIO: - drop interrupt support until we have correct implementation of hierarchical irqs in gpiolib v2 -> v3: ========= General: - dropped regulator patches as they're already in Mark Brown's branch LED: - fix the compatible string in the DT binding example - use the max_brightness property - use a common prefix ("MAX77650_LED") for all defines in the driver MFD: - add the MODULE_DEVICE_TABLE() - add a sentinel to the of_device_id array - constify the pointers to irq names - use an enum instead of defines for interrupt indexes v3 -> v4: ========= GPIO: - as discussed with Linus Walleij: the gpio-controller is now part of the core mfd module (we don't spawn a sub-node anymore), the binding document for GPIO has been dropped, the GPIO properties have been defined in the binding document for the mfd core, the interrupt functionality has been reintroduced with the irq directly passed from the mfd part - due to the above changes the Reviewed-by tag from Linus was dropped v4 -> v5: ========= General: - add a patch documenting mfd_add_devices() MFD: - pass the regmap irq_chip irq domain to mfd over mfd_add_devices so that the hw interrupts from resources can be correctly mapped to virtual irqs - remove the enum listing cell indexes - extend Kconfig help - add a link to the programming manual - use REGMAP_IRQ_REG() for regmap interrupts (except for GPI which has is composed of two hw interrupts for rising and falling edge) - add error messages in probe - use PLATFORM_DEVID_NONE constant in devm_mfd_add_devices() - set irq_base to 0 in regmap_add_irq_chip() as other users to, it's only relevant if it's > 0 Charger: - use non-maxim specific property names for minimum input voltage and current limit - code shrink by using the enable/disable charger helpers everywhere - use more descriptive names for constants Onkey: - use EV_SW event type for slide mode LED: - remove stray " from Kconfig help Bartosz Golaszewski (11): dt-bindings: mfd: add DT bindings for max77650 dt-bindings: power: supply: add DT bindings for max77650 dt-bindings: leds: add DT bindings for max77650 dt-bindings: input: add DT bindings for max77650 mfd: core: document mfd_add_devices() mfd: max77650: new core mfd driver power: supply: max77650: add support for battery charger gpio: max77650: add GPIO support leds: max77650: add LEDs support input: max77650: add onkey support MAINTAINERS: add an entry for max77650 mfd driver .../bindings/input/max77650-onkey.txt | 26 ++ .../bindings/leds/leds-max77650.txt | 57 +++ .../devicetree/bindings/mfd/max77650.txt | 47 +++ .../power/supply/max77650-charger.txt | 27 ++ MAINTAINERS | 14 + drivers/gpio/Kconfig | 7 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-max77650.c | 190 ++++++++++ drivers/input/misc/Kconfig | 9 + drivers/input/misc/Makefile | 1 + drivers/input/misc/max77650-onkey.c | 131 +++++++ drivers/leds/Kconfig | 6 + drivers/leds/Makefile | 1 + drivers/leds/leds-max77650.c | 147 ++++++++ drivers/mfd/Kconfig | 14 + drivers/mfd/Makefile | 1 + drivers/mfd/max77650.c | 234 ++++++++++++ drivers/mfd/mfd-core.c | 14 + drivers/power/supply/Kconfig | 7 + drivers/power/supply/Makefile | 1 + drivers/power/supply/max77650-charger.c | 353 ++++++++++++++++++ include/linux/mfd/max77650.h | 59 +++ 22 files changed, 1347 insertions(+) create mode 100644 Documentation/devicetree/bindings/input/max77650-onkey.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-max77650.txt create mode 100644 Documentation/devicetree/bindings/mfd/max77650.txt create mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.txt create mode 100644 drivers/gpio/gpio-max77650.c create mode 100644 drivers/input/misc/max77650-onkey.c create mode 100644 drivers/leds/leds-max77650.c create mode 100644 drivers/mfd/max77650.c create mode 100644 drivers/power/supply/max77650-charger.c create mode 100644 include/linux/mfd/max77650.h