From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Matthijs van Duin" <matthijsvanduin@gmail.com>,
"David Rivshin" <drivshin@allworx.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
"Marek Belisko" <marek@goldelico.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"Discussions about the Letux Kernel"
<letux-kernel@openphoenux.org>,
"Neil Armstrong" <narmstrong@baylibre.com>
Subject: Re: [PATCH] ARM: dts: omap3-gta04: reduce panel backlight PWM frequency to 83Hz
Date: Tue, 13 Sep 2016 15:07:13 -0700 [thread overview]
Message-ID: <20160913220710.wo7jjyql362pttbs@atomide.com> (raw)
In-Reply-To: <7C9DF12E-32C6-4D7C-BAAD-5CE9F8BA305A@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [160910 02:10]:
> > Am 10.09.2016 um 10:20 schrieb Matthijs van Duin <matthijsvanduin@gmail.com>:
>
> But with the patch submitted, I just want to give the dts of a single
> device I have even designed a more reasonable value than in current
> linux/master and don't really want to make it a fundamental discussion...
So what's the verdict here on this patch? Should we wait for the driver
to get fixed?
Regards,
Tony
next prev parent reply other threads:[~2016-09-13 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 9:16 H. Nikolaus Schaller
2016-09-10 3:17 ` Matthijs van Duin
2016-09-10 7:08 ` H. Nikolaus Schaller
2016-09-10 7:14 ` [Letux-kernel] " H. Nikolaus Schaller
2016-09-10 8:20 ` Matthijs van Duin
2016-09-10 9:10 ` H. Nikolaus Schaller
2016-09-13 22:07 ` Tony Lindgren [this message]
2016-09-14 4:28 ` H. Nikolaus Schaller
2016-09-14 18:12 ` Tony Lindgren
2016-09-10 13:48 ` Neil Armstrong
2016-09-12 14:41 ` David Rivshin
2016-09-12 15:03 ` Neil Armstrong
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=20160913220710.wo7jjyql362pttbs@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=drivshin@allworx.com \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marek@goldelico.com \
--cc=mark.rutland@arm.com \
--cc=matthijsvanduin@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®