[PATCH linux v1 0/4] Seven segment display support

[Joel Stanley]

Hello Jagha,

On Tue, Feb 7, 2017 at 2:33 PM, Jaghathiswari Rankappagounder
Natarajan <jaghu at google.com> wrote:
> Hi Joel,
> Nancy mentioned this patch can be included into openbmc linux tree now.
> Some other member will take up the work of addressing the comments from
> upstream reviewers and send the patch upstream.

Just before you sent these patches we had a chat on the topic. I
thought we decided to give the rest of this week for people to review
the new process, and then on Monday I would publish a tree based on
4.10 that you could submit patches to. Sorry for not making this
clear.

I suspect this set will apply to 4.10 as-is, so I will consider this
your submission for the 4.10 tree next week.

Next time please have a read of the development process[1] and the
rules for submitting patches[2] before sending patches. In particular,
you need to set the target branch in the subject line so I know where
you want the patches applied. If you you have any questions about the
process please let me know so I can update the documentation.

[1] https://github.com/openbmc/linux/wiki/DevelopmentProcess
[2] https://github.com/openbmc/linux/wiki/SubmittingPatches

Cheers,

Joel

>
> This patchset includes:
>
> Documentation for the binding which provides an interface for adding clock,
> data and clear signal GPIO lines to control seven segment display.
>
> The platform device driver provides an API for displaying on two 7-segment
> displays, and implements the required bit-banging. The hardware assumed is
> 74HC164 wired to two 7-segment displays.
>
> The character device driver implements the user-space API for letting a user
> write to two 7-segment displays including any conversion methods necessary
> to map the user input to two 7-segment displays.
>
> Adding clock, data and clear signal GPIO lines in the devicetree to control
> seven segment display on zaius platform.
>
> The platform driver matches on the device tree node; the platform driver also
> initializes the character device.
>
> Tested that the seven segment display works properly by writing to the
> character device file on a EVB AST2500 board which also has 74HC164 wired
> to two 7-segment displays.
>
> Jaghathiswari Rankappagounder Natarajan (4):
>   Documentation: dt-bindings: Document bindings for seven segment
>     display support
>   drivers: misc: Character device driver for seven segment display
>   drivers: misc: Platform driver for seven segment display support
>   arm: dts: Add dt-binding to support seven segment display on zaius
>
>  .../devicetree/bindings/misc/seven-seg-gpio.txt    |  27 +++
>  arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts         |   8 +
>  drivers/misc/Kconfig                               |  16 ++
>  drivers/misc/Makefile                              |   2 +
>  drivers/misc/seven_seg_disp.c                      | 201 ++++++++++++++++++++
>  drivers/misc/seven_seg_disp.h                      |  34 ++++
>  drivers/misc/seven_seg_gpio.c                      | 206 +++++++++++++++++++++
>  7 files changed, 494 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/misc/seven-seg-gpio.txt
>  create mode 100644 drivers/misc/seven_seg_disp.c
>  create mode 100644 drivers/misc/seven_seg_disp.h
>  create mode 100644 drivers/misc/seven_seg_gpio.c
>
> --
> 2.11.0.483.g087da7b7c-goog
>