devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Andreas Kemnade" <andreas@kemnade.info>,
	"Discussions about the Letux Kernel"
	<letux-kernel@openphoenux.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Benoît Cousson" <bcousson@baylibre.com>
Subject: Re: [Letux-kernel] [PATCH 2/2] DTS: ARM: gta04: introduce legacy spi-cs-high to make display work again
Date: Fri, 20 Sep 2019 08:53:06 -0700	[thread overview]
Message-ID: <20190920155306.GT5610@atomide.com> (raw)
In-Reply-To: <96E62EC2-2A3E-4722-A9DE-3F320B0A98B0@goldelico.com>

* H. Nikolaus Schaller <hns@goldelico.com> [190920 15:50]:
> 
> > Am 20.09.2019 um 17:29 schrieb Andreas Kemnade <andreas@kemnade.info>:
> > 
> > On Fri, 20 Sep 2019 16:54:18 +0200
> > "H. Nikolaus Schaller" <hns@goldelico.com> wrote:
> > 
> >>> Am 20.09.2019 um 16:20 schrieb Tony Lindgren <tony@atomide.com>:
> >>> 
> >>> * H. Nikolaus Schaller <hns@goldelico.com> [190920 09:19]:  
> >>>>> Am 20.09.2019 um 10:55 schrieb Linus Walleij <linus.walleij@linaro.org>:
> >>>>> I suggest to go both way:
> >>>>> apply this oneliner and tag for stable so that GTA04 works
> >>>>> again.
> >>>>> 
> >>>>> Then for the next kernel think about a possible more abitious
> >>>>> whitelist solution and after adding that remove *all* "spi-cs-high"
> >>>>> flags from all device trees in the kernel after fixing them
> >>>>> all up.  
> >>>> 
> >>>> Ok, that looks like a viable path.  
> >>> 
> >>> Please repost the oneline so people can ack easily. At least
> >>> I've already lost track of this thread.  
> >> 
> >> It is all here:
> >> 
> >> https://patchwork.kernel.org/patch/11035253/
> >> 
> > It is the full one (incl. documentation), not the oneline and does not
> > apply.
> 
> Looks as if it was sitting too long in the queue and linux-next has changed
> the basis in the meantime, while v5.3 has not yet.
> 
> Documentation/devicetree/bindings/spi/spi-bus.txt -> spi-controller.yaml
> 
> So it should still apply for v5.3.1 and earlier and we need both versions.
> One for stable and one for linux-next. I don't know how to handle such cases.

Please just repost a minimal dts one line fix. Then a separate
patch for the documentation changes.

Regards,

Tony

  reply	other threads:[~2019-09-20 15:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 14:46 [PATCH 0/2] DTS: ARM: some minor updates and fixes for GTA04 H. Nikolaus Schaller
2019-07-08 14:46 ` [PATCH 1/2] DTS: ARM: gta04: define chosen/stdout-path H. Nikolaus Schaller
2019-08-13 11:47   ` Tony Lindgren
2019-07-08 14:46 ` [PATCH 2/2] DTS: ARM: gta04: introduce legacy spi-cs-high to make display work again H. Nikolaus Schaller
2019-07-24 19:42   ` Rob Herring
2019-07-25  6:23     ` H. Nikolaus Schaller
2019-07-25 22:42       ` Rob Herring
2019-08-05 10:29         ` Linus Walleij
2019-08-31  6:48           ` [Letux-kernel] " Andreas Kemnade
2019-09-16 10:59             ` H. Nikolaus Schaller
2019-09-16 22:52               ` Linus Walleij
2019-09-17 14:26                 ` H. Nikolaus Schaller
2019-09-20  8:55                   ` Linus Walleij
2019-09-20  9:19                     ` H. Nikolaus Schaller
2019-09-20 14:20                       ` Tony Lindgren
2019-09-20 14:54                         ` H. Nikolaus Schaller
2019-09-20 15:29                           ` Andreas Kemnade
2019-09-20 15:50                             ` H. Nikolaus Schaller
2019-09-20 15:53                               ` Tony Lindgren [this message]
2019-09-20 15:55                               ` H. Nikolaus Schaller

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=20190920155306.GT5610@atomide.com \
    --to=tony@atomide.com \
    --cc=andreas@kemnade.info \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).