| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-id: <1420816989-1808-1-git-send-email-j.anaszewski@samsung.com> Date: Fri, 09 Jan 2015 16:22:50 +0100 From: Jacek Anaszewski <j.anaszewski@...sung.com> To: linux-leds@...r.kernel.org, linux-media@...r.kernel.org, linux-kernel@...r.kernel.org Cc: devicetree@...r.kernel.org, kyungmin.park@...sung.com, b.zolnierkie@...sung.com, pavel@....cz, cooloney@...il.com, rpurdie@...ys.net, sakari.ailus@....fi, s.nawrocki@...sung.com, Jacek Anaszewski <j.anaszewski@...sung.com> Subject: [PATCH/RFC v10 00/19] LED / flash API integration This patch set is a follow-up of the LED / flash API integration series [1]. It is based on linux-next_20150108. ======================== Changes since version 9 : ======================== - switched to assigning sub-led related of_node to led_cdev->dev->of_node member which allowed for avoiding modifications around v4l-async - reimplemented max77693 flash cell driver to avoid extensive use of macros - added led-sources DT property and switched to using it - switched to reporting flash faults in the LED subsystem in the form of human readable strings - added available_sync_leds sysfs attribute to the LED Flash class and changed the semantics of flash_sync_strobe attribute - made LED subsystem flash faults not depending on the V4L2 Flash ones - applied various fixes and cleanups ======================== Changes since version 8: ======================== - added a new way of registering async sub-device - switched to matching flash leds by DT phandles - improved Device Tree bindings documentation - split the drivers patches to LED Flash class and V4L2 Flash part - fixed indicator leds handling in v4l2-flash - applied various fixes an cleanups ======================== Changes since version 7: ======================== - removed explicit support for indicator leds from LED Flash class - indicator leds will be registered as a separate LED Flash class devices - added flash_sync_strobe sysfs attribute and related V4L2_CID_FLASH_SYNC_STROBE control - changed the way of matching V4L2 Flash sub-devices in a media device, which entailed modification in v4l2-async driver - modified max77693 DT bindings documentation - applied various fixes an cleanups ======================== Changes since version 6: ======================== - removed addition of public LED subsystem API for setting torch brightness in favour of internal API for synchronous and asynchronous led brightness level setting - fixed possible race condition upon creating LED Flash class related sysfs attributes ======================== Changes since version 5: ======================== - removed flash manager framework - its implementation needs further thorough discussion. - removed external strobe facilities from the LED Flash Class and provided external_strobe_set op in v4l2-flash. LED subsystem should be strobe provider agnostic. Thanks, Jacek Anaszewski [1] https://lkml.org/lkml/2014/7/11/914 Jacek Anaszewski (19): leds: Add LED Flash class extension to the LED subsystem Documentation: leds: Add description of LED Flash class extension DT: leds: Add led-sources property dt-binding: mfd: max77693: Add DT binding related macros mfd: max77693: Modify flash cell name identifiers mfd: max77693: modifications around max77693_led_platform_data mfd: max77693: Adjust FLASH_EN_SHIFT and TORCH_EN_SHIFT macros leds: Add support for max77693 mfd flash cell DT: Add documentation for the mfd Maxim max77693 leds: Add driver for AAT1290 current regulator of: Add Skyworks Solutions, Inc. vendor prefix DT: Add documentation for the Skyworks AAT1290 exynos4-is: Add support for v4l2-flash subdevs v4l2-ctrls: Add V4L2_CID_FLASH_SYNC_STROBE control media: Add registration helpers for V4L2 flash sub-devices Documentation: leds: Add description of v4l2-flash sub-device DT: Add documentation for exynos4-is 'flashes' property leds: max77693: add support for V4L2 Flash sub-device leds: aat1290: add support for V4L2 Flash sub-device Documentation/DocBook/media/v4l/controls.xml | 9 + Documentation/devicetree/bindings/leds/common.txt | 5 + .../devicetree/bindings/leds/leds-aat1290.txt | 17 + .../devicetree/bindings/media/samsung-fimc.txt | 7 + Documentation/devicetree/bindings/mfd/max77693.txt | 69 ++ .../devicetree/bindings/vendor-prefixes.txt | 1 + Documentation/leds/leds-class-flash.txt | 70 ++ drivers/leds/Kconfig | 27 + drivers/leds/Makefile | 3 + drivers/leds/led-class-flash.c | 486 ++++++++ drivers/leds/led-class.c | 4 + drivers/leds/leds-aat1290.c | 460 ++++++++ drivers/leds/leds-max77693.c | 1178 ++++++++++++++++++++ drivers/media/platform/exynos4-is/media-dev.c | 36 +- drivers/media/platform/exynos4-is/media-dev.h | 13 +- drivers/media/v4l2-core/Kconfig | 11 + drivers/media/v4l2-core/Makefile | 2 + drivers/media/v4l2-core/v4l2-ctrls.c | 2 + drivers/media/v4l2-core/v4l2-flash.c | 581 ++++++++++ drivers/mfd/max77693.c | 4 +- include/dt-bindings/mfd/max77693.h | 21 + include/linux/led-class-flash.h | 207 ++++ include/linux/leds.h | 3 + include/linux/mfd/max77693-private.h | 4 +- include/linux/mfd/max77693.h | 9 +- include/media/v4l2-flash.h | 139 +++ include/uapi/linux/v4l2-controls.h | 1 + 27 files changed, 3357 insertions(+), 12 deletions(-) create mode 100644 Documentation/devicetree/bindings/leds/leds-aat1290.txt create mode 100644 Documentation/leds/leds-class-flash.txt create mode 100644 drivers/leds/led-class-flash.c create mode 100644 drivers/leds/leds-aat1290.c create mode 100644 drivers/leds/leds-max77693.c create mode 100644 drivers/media/v4l2-core/v4l2-flash.c create mode 100644 include/dt-bindings/mfd/max77693.h create mode 100644 include/linux/led-class-flash.h create mode 100644 include/media/v4l2-flash.h -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists