The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: SUNGOLD <suraajvashisht@gmail.com>
Cc: linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org
Subject: Re: drivers: mfd: lm3533: Support for DT bindings
Date: Wed, 9 Sep 2020 08:28:56 +0100	[thread overview]
Message-ID: <20200909072856.GB4400@dell> (raw)
In-Reply-To: <CAFiUnPa-6eRCPhz0omojCUi-OxQmCk3YoX3NF_n9mx3bz6fc7w@mail.gmail.com>

On Thu, 03 Sep 2020, SUNGOLD wrote:

> Hi, I am a high school student and a Linux enthusiast and for my free time,
> I'm trying to mainline a spare device I had, it's a Xiaomi Mi 4i
> (xiaomi-ferrari), till now I've got some basic bringup (had to bring up
> touchscreen Atmel mXT336T using the downstream driver as the mainlined
> generic atmel_mxt_ts.c has no support, so committed a sin
> <https://github.com/SUNGOLDSV/msm8916-mainline-linux/commit/6280fdb9750b1dc40dd4d769118d8ba71cbb0a0d>
> ;)
> 
> I'm currently working on implementing backlight for my panel and it uses
> LM3533 for it's backlight and notification LEDS.
> 
> I tried to find any dt-bindings docs about it and I finally found a patch
> <http://patchwork.ozlabs.org/project/devicetree-bindings/patch/20161226181153.11271-1-bjorn.andersson@linaro.org/#1545653>
> that was rejected and I followed it in hopes of initialising the driver,
> and it didn't work out as it was not even initialising.
> 
> With me having almost no knowledge of C, I tried to understand the
> `lm3533-core.c` while reading some docs on building a linux driver, and my
> interpretation is that the driver was not written for devices that use DTS
> and it was actually written for devices that use a board config file such
> as imx arm based devices.
> 
> Now I request you to add support for devices that use DTS or I might have
> to commit another sin ;)
> 
> My Github repo <https://github.com/SUNGOLDSV/msm8916-mainline-linux>
> 
> Thanking you
> sungold
> p.s. just asking for advice and help, this is my first mail to a dev and a
> mailing list

Good morning,

Thanks for reaching out.

I think your best bet is to follow-up with Bjorn (now Cc'ed).

Keep up the good work.

Kind regards,
Lee

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

           reply	other threads:[~2020-09-09  7:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAFiUnPa-6eRCPhz0omojCUi-OxQmCk3YoX3NF_n9mx3bz6fc7w@mail.gmail.com>]

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=20200909072856.GB4400@dell \
    --to=lee.jones@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suraajvashisht@gmail.com \
    /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