From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Fenglin Wu <fenglinw@codeaurora.org>
Subject: Re: [PATCH v2 0/3] Qualcomm Light Pulse Generator
Date: Sun, 16 Jul 2017 13:53:04 -0700 [thread overview]
Message-ID: <20170716205304.GU1618@tuxbook> (raw)
In-Reply-To: <20170706031813.GC12954@xo-6d-61-c0.localdomain>
On Wed 05 Jul 20:18 PDT 2017, Pavel Machek wrote:
> Hi!
>
> > > > DT: leds: Add Qualcomm Light Pulse Generator binding
> > >
> > > This one should be first.
> > >
> >
> > Okay, no problems.
> >
> > > And I guess I'd prefer the driver to go in first, before the generic
> > > pattern interface.
> > >
> >
> > The driver won't compile without the additions to the header file. Would
> > you like the rest of the driver to go in first, then the generic
> > interface and finally the pattern part of the driver?
> >
> > Large portions of the driver doesn't make sense without the pattern
> > part, so I think I would prefer it to go in as one patch.
>
> Can we get minimum driver without the pattern parts?
>
It's possible to do, but I must admit I find it slightly contrived.
The overall design of different parts of the driver does relate to how I
decided to structure and implement the pattern support, so this would
mean that the driver we merge has a conceptual dependency on a
out-of-tree part.
May I ask about the reasoning for your request? Is it just to not leave
the driver hanging while we conclude the discussion on the pattern
interface?
Regards,
Bjorn
next prev parent reply other threads:[~2017-07-16 20:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 22:45 [PATCH v2 0/3] Qualcomm Light Pulse Generator Bjorn Andersson
2017-07-14 22:45 ` [PATCH v2 1/3] leds: core: Introduce generic pattern interface Bjorn Andersson
2017-07-06 3:18 ` Pavel Machek
2017-07-16 18:49 ` Jacek Anaszewski
2017-07-16 21:14 ` Bjorn Andersson
2017-07-17 21:08 ` Jacek Anaszewski
2017-07-17 23:39 ` Bjorn Andersson
2017-07-18 21:36 ` Jacek Anaszewski
2017-08-12 19:22 ` Pavel Machek
2017-07-16 19:57 ` Bjorn Andersson
2017-07-14 22:45 ` [PATCH v2 2/3] leds: Add driver for Qualcomm LPG Bjorn Andersson
2017-07-14 22:45 ` [PATCH v2 3/3] DT: leds: Add Qualcomm Light Pulse Generator binding Bjorn Andersson
2017-07-15 9:14 ` Pavel Machek
2017-07-16 5:35 ` Bjorn Andersson
2017-07-16 18:49 ` Jacek Anaszewski
2017-07-17 4:44 ` Bjorn Andersson
2017-07-17 21:08 ` Jacek Anaszewski
2017-07-18 0:03 ` Bjorn Andersson
2017-07-18 21:38 ` Jacek Anaszewski
2017-07-15 9:10 ` [PATCH v2 0/3] Qualcomm Light Pulse Generator Pavel Machek
2017-07-16 5:34 ` Bjorn Andersson
2017-07-06 3:18 ` Pavel Machek
2017-07-16 20:53 ` Bjorn Andersson [this message]
2017-07-16 21:15 ` Pavel Machek
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=20170716205304.GU1618@tuxbook \
--to=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fenglinw@codeaurora.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/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