Re: [PATCH] MIPS: generic: Update node names to avoid unit addresses

1a353f4b127ed57279279f851c6b4917 > Suggested-by: Simon Glass > Signed-off-by: Nathan Chancellor Reviewed-by: Tom Rini -- Tom signature.asc Description: PGP signature

Re: [SPECIFICATION RFC] The firmware and bootloader log specification

On Fri, Dec 04, 2020 at 02:23:23PM +0100, Paul Menzel wrote: > Dear Wim, dear Daniel, > > > First, thank you for including all parties in the discussion. > Am 04.12.20 um 13:52 schrieb Wim Vervoorn: > > > I agree with you. Using an existing standard is better than inventing > > a new one in

Re: [PATCH] initrd: Remove erroneous comment

On Mon, Jun 22, 2020 at 02:03:28PM -0700, H. Peter Anvin wrote: > On 2020-06-22 14:01, Tom Rini wrote: > > > > I'm picky here because, well, there's a whole lot of moving parts in the > > pre-kernel world. In a strict sense, "UEFI" doesn't do anything with &g

Re: [PATCH] initrd: Remove erroneous comment

On Mon, Jun 22, 2020 at 01:48:45PM -0700, H. Peter Anvin wrote: > On 2020-06-22 13:40, Tom Rini wrote: > > On Mon, Jun 22, 2020 at 01:02:16PM -0700, ron minnich wrote: > > > >> The other thing you ought to consider fixing: > >> initrd is documented as

Re: [PATCH] initrd: Remove erroneous comment

On Mon, Jun 22, 2020 at 01:56:24PM -0700, ron minnich wrote: > So, let me first add, the comment can be removed as needed. Comments > offered only for clarification. Noted, thanks. > On Mon, Jun 22, 2020 at 1:40 PM Tom Rini wrote: > > > But what do you mean UEFI

Re: [PATCH] initrd: Remove erroneous comment

On Mon, Jun 22, 2020 at 01:02:16PM -0700, ron minnich wrote: > The other thing you ought to consider fixing: > initrd is documented as follows: > > initrd= [BOOT] Specify the location of the initial ramdisk > > for bootloaders only. > > UEFI consumes initrd from the command

[tip: x86/cleanups] initrd: Remove erroneous comment

The following commit has been merged into the x86/cleanups branch of tip: Commit-ID: eacb0c101a0bdf14de77cc9d107493e2d8d6389c Gitweb: https://git.kernel.org/tip/eacb0c101a0bdf14de77cc9d107493e2d8d6389c Author:Tom Rini AuthorDate:Fri, 19 Jun 2020 10:30:56 -04:00 Committer

[PATCH] initrd: Remove erroneous comment

") Cc: Andrew Morton Cc: Borislav Petkov Cc: Dominik Brodowski Cc: H. Peter Anvin (Intel) Cc: Ronald G. Minnich Signed-off-by: Tom Rini --- For a bit more context, I assume there's been some confusion between "initrd" being a keyword in things like extlinux.conf and also that for q

Re: [U-Boot] [v4 PATCH] RISCV: image: Add booti support

On Mon, May 06, 2019 at 11:10:57PM +0200, Heinrich Schuchardt wrote: > On 5/6/19 10:39 PM, Karsten Merker wrote: > >On Mon, May 06, 2019 at 10:06:39PM +0200, Heinrich Schuchardt wrote: > >>On 5/6/19 8:11 PM, Atish Patra wrote: > >>>This patch adds booti support for RISC-V Linux kernel. The

Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

On Thu, Oct 05, 2017 at 10:09:39AM -0500, Rob Herring wrote: > On Thu, Oct 5, 2017 at 9:39 AM, Tom Rini <tr...@konsulko.com> wrote: > > On Tue, Oct 03, 2017 at 05:23:28PM -0500, Rob Herring wrote: > >> On Tue, Oct 3, 2017 at 5:04 PM, Tom Rini <tr...@konsulko.com> wrot

Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

On Thu, Oct 05, 2017 at 10:09:39AM -0500, Rob Herring wrote: > On Thu, Oct 5, 2017 at 9:39 AM, Tom Rini wrote: > > On Tue, Oct 03, 2017 at 05:23:28PM -0500, Rob Herring wrote: > >> On Tue, Oct 3, 2017 at 5:04 PM, Tom Rini wrote: > >> > On Tue, Oct 03, 2017 at 01:31

Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

On Tue, Oct 03, 2017 at 05:23:28PM -0500, Rob Herring wrote: > On Tue, Oct 3, 2017 at 5:04 PM, Tom Rini <tr...@konsulko.com> wrote: > > On Tue, Oct 03, 2017 at 01:31:17PM -0500, Rob Herring wrote: > > > >> libfdt has gained some new files. We need to include

Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

On Tue, Oct 03, 2017 at 05:23:28PM -0500, Rob Herring wrote: > On Tue, Oct 3, 2017 at 5:04 PM, Tom Rini wrote: > > On Tue, Oct 03, 2017 at 01:31:17PM -0500, Rob Herring wrote: > > > >> libfdt has gained some new files. We need to include them in the > >> kernel's

Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

On Tue, Oct 03, 2017 at 01:31:17PM -0500, Rob Herring wrote: > libfdt has gained some new files. We need to include them in the > kernel's copy. > > Reported-by: Kyle Yan > Signed-off-by: Rob Herring > --- > scripts/dtc/update-dtc-source.sh | 4 +++- > 1

Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

On Tue, Oct 03, 2017 at 01:31:17PM -0500, Rob Herring wrote: > libfdt has gained some new files. We need to include them in the > kernel's copy. > > Reported-by: Kyle Yan > Signed-off-by: Rob Herring > --- > scripts/dtc/update-dtc-source.sh | 4 +++- > 1 file changed, 3 insertions(+), 1

Problems with Chromebook Pixel 2015 audio

Hey folks, Entirely unrelated to the regression on this board that we dealt with the other week, I have (and have had for a bit), a problem with audio on this laptop. After a while of use, I'll have a problem like this: Sep 12 20:59:30 oliver kernel: haswell-pcm-audio haswell-pcm-audio: FW

Problems with Chromebook Pixel 2015 audio

Hey folks, Entirely unrelated to the regression on this board that we dealt with the other week, I have (and have had for a bit), a problem with audio on this laptop. After a while of use, I'll have a problem like this: Sep 12 20:59:30 oliver kernel: haswell-pcm-audio haswell-pcm-audio: FW

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Fri, Aug 25, 2017 at 07:42:51PM +0300, Andy Shevchenko wrote: > On Fri, 2017-08-25 at 17:05 +0100, John Keeping wrote: > > On Fri, 25 Aug 2017 10:24:26 -0400, Tom Rini wrote: > > > On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote: > > > > > Appa

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Fri, Aug 25, 2017 at 07:42:51PM +0300, Andy Shevchenko wrote: > On Fri, 2017-08-25 at 17:05 +0100, John Keeping wrote: > > On Fri, 25 Aug 2017 10:24:26 -0400, Tom Rini wrote: > > > On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote: > > > > > Appa

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote: > +John > > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > Not all devices with ACPI and this combination of sound devices will > > have the required information provided via ACPI.  Reintroduce

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote: > +John > > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > Not all devices with ACPI and this combination of sound devices will > > have the required information provided via ACPI.  Reintroduce

Re: [alsa-devel] [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 06:06:20PM +0200, Takashi Iwai wrote: > On Thu, 24 Aug 2017 17:54:37 +0200, > Tom Rini wrote: > > > > On Thu, Aug 24, 2017 at 04:52:35PM +0100, Mark Brown wrote: > > > On Thu, Aug 24, 2017 at 05:42:11PM +0200, Takashi Iwai wrote: > > &

Re: [alsa-devel] [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 06:06:20PM +0200, Takashi Iwai wrote: > On Thu, 24 Aug 2017 17:54:37 +0200, > Tom Rini wrote: > > > > On Thu, Aug 24, 2017 at 04:52:35PM +0100, Mark Brown wrote: > > > On Thu, Aug 24, 2017 at 05:42:11PM +0200, Takashi Iwai wrote: > > &

Re: [alsa-devel] [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 04:52:35PM +0100, Mark Brown wrote: > On Thu, Aug 24, 2017 at 05:42:11PM +0200, Takashi Iwai wrote: > > > OK, so the fix for 4.13 would be either to cherry-pick this commit, or > > just to re-add "RT5677CE:00" to i2c_id temporarily as a quick band-aid > > fix (and remove

Re: [alsa-devel] [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 04:52:35PM +0100, Mark Brown wrote: > On Thu, Aug 24, 2017 at 05:42:11PM +0200, Takashi Iwai wrote: > > > OK, so the fix for 4.13 would be either to cherry-pick this commit, or > > just to re-add "RT5677CE:00" to i2c_id temporarily as a quick band-aid > > fix (and remove

Re: [alsa-devel] [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 04:31:25PM +0200, Takashi Iwai wrote: > On Thu, 24 Aug 2017 16:28:29 +0200, > Takashi Iwai wrote: > > > > On Thu, 24 Aug 2017 02:05:25 +0200, > > Tom Rini wrote: > > > > > > On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wr

Re: [alsa-devel] [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 04:31:25PM +0200, Takashi Iwai wrote: > On Thu, 24 Aug 2017 16:28:29 +0200, > Takashi Iwai wrote: > > > > On Thu, 24 Aug 2017 02:05:25 +0200, > > Tom Rini wrote: > > > > > > On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wr

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 03:26:00PM +0300, Andy Shevchenko wrote: > On Thu, 2017-08-24 at 07:15 -0400, Tom Rini wrote: > > On Thu, Aug 24, 2017 at 10:39:09AM +0300, Andy Shevchenko wrote: > > > On Wed, 2017-08-23 at 20:05 -0400, Tom Rini wrote: > > > > On Wed, Aug 23,

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 03:26:00PM +0300, Andy Shevchenko wrote: > On Thu, 2017-08-24 at 07:15 -0400, Tom Rini wrote: > > On Thu, Aug 24, 2017 at 10:39:09AM +0300, Andy Shevchenko wrote: > > > On Wed, 2017-08-23 at 20:05 -0400, Tom Rini wrote: > > > > On Wed, Aug 23,

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 10:39:09AM +0300, Andy Shevchenko wrote: > On Wed, 2017-08-23 at 20:05 -0400, Tom Rini wrote: > > On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote: > > > On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > > > > >

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Thu, Aug 24, 2017 at 10:39:09AM +0300, Andy Shevchenko wrote: > On Wed, 2017-08-23 at 20:05 -0400, Tom Rini wrote: > > On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote: > > > On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > > > > >

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote: > On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > > > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > > Not all devices with ACPI and this combination of sound devices will > > >

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote: > On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > > > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > > Not all devices with ACPI and this combination of sound devices will > > >

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 11:47:52PM +0100, Mark Brown wrote: > On Wed, Aug 23, 2017 at 06:35:24PM -0400, Tom Rini wrote: > > > After looking at 89128534f925 (which introduced the above line, and thus > > Please include human readable descriptions of things like commits

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 11:47:52PM +0100, Mark Brown wrote: > On Wed, Aug 23, 2017 at 06:35:24PM -0400, Tom Rini wrote: > > > After looking at 89128534f925 (which introduced the above line, and thus > > Please include human readable descriptions of things like commits

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

[stupid google spam filtered _this_ as spam, I don't know why] On Wed, Aug 23, 2017 at 10:28:28AM +0100, Mark Brown wrote: > On Tue, Aug 22, 2017 at 09:51:46PM -0400, Tom Rini wrote: > > > Not all devices with ACPI and this combination of sound devices will > > have the re

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

[stupid google spam filtered _this_ as spam, I don't know why] On Wed, Aug 23, 2017 at 10:28:28AM +0100, Mark Brown wrote: > On Tue, Aug 22, 2017 at 09:51:46PM -0400, Tom Rini wrote: > > > Not all devices with ACPI and this combination of sound devices will > > have the re

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > Not all devices with ACPI and this combination of sound devices will > > have the required information provided via ACPI.  Reintroduce the I2C > > devic

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > Not all devices with ACPI and this combination of sound devices will > > have the required information provided via ACPI.  Reintroduce the I2C > > devic

[PATCH] ASoC: rt5677: Reintroduce I2C device IDs

.org Cc: Andy Shevchenko <andriy.shevche...@linux.intel.com> Cc: Mark Brown <broo...@kernel.org> Cc: Linus Torvalds <torva...@linux-foundation.org> Signed-off-by: Tom Rini <tr...@konsulko.com> --- This is a regression from v4.12 on my laptop (a Chromebook 'Samus' that's not running

[PATCH] ASoC: rt5677: Reintroduce I2C device IDs

ation") Cc: Bard Liao Cc: Oder Chiou Cc: Liam Girdwood Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: alsa-de...@alsa-project.org CC: linux-kernel@vger.kernel.org Cc: Andy Shevchenko Cc: Mark Brown Cc: Linus Torvalds Signed-off-by: Tom Rini --- This is a regression from v4.12 on my laptop (a

Re: [PATCH] dts: Make it easier to enable __symbols__ generation in dtb files

On Wed, Aug 16, 2017 at 11:32:08PM -0700, Frank Rowand wrote: > Hi Tom, > > Some nit picking on the patch comment. :-) > > > On 08/16/17 17:35, Tom Rini wrote: > > This introduces the variabe DTC_EXTRA_FLAGS to allow for additional > > flags to be passed to dtc.

Re: [PATCH] dts: Make it easier to enable __symbols__ generation in dtb files

On Wed, Aug 16, 2017 at 11:32:08PM -0700, Frank Rowand wrote: > Hi Tom, > > Some nit picking on the patch comment. :-) > > > On 08/16/17 17:35, Tom Rini wrote: > > This introduces the variabe DTC_EXTRA_FLAGS to allow for additional > > flags to be passed to dtc.

[PATCH] dts: Make it easier to enable __symbols__ generation in dtb files

-ker...@lists.infradead.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Tom Rini <tr...@konsulko.com> --- This would be v3 of my attempt to enable __symbols__ more widely (v2, for people not on the CC, enabled it always, but for some boards). To be clear, this version of the patch is more

[PATCH] dts: Make it easier to enable __symbols__ generation in dtb files

-arm-ker...@lists.infradead.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Tom Rini --- This would be v3 of my attempt to enable __symbols__ more widely (v2, for people not on the CC, enabled it always, but for some boards). To be clear, this version of the patch is more flexible

Re: [PATCH] ARM: dts: TI: Enable __symbols__ in dtb files for some platforms

On Wed, Aug 16, 2017 at 03:57:21PM -0700, Frank Rowand wrote: > On 08/16/17 15:33, Frank Rowand wrote: > > On 08/16/17 14:59, Tom Rini wrote: > >> Build the dtb file for these platfroms with __symbol__ information > >> included. This will reduce the size of t

Re: [PATCH] ARM: dts: TI: Enable __symbols__ in dtb files for some platforms

On Wed, Aug 16, 2017 at 03:57:21PM -0700, Frank Rowand wrote: > On 08/16/17 15:33, Frank Rowand wrote: > > On 08/16/17 14:59, Tom Rini wrote: > >> Build the dtb file for these platfroms with __symbol__ information > >> included. This will reduce the size of t

[PATCH] ARM: dts: TI: Enable __symbols__ in dtb files for some platforms

h...@kernel.org> Cc: Mark Rutland <mark.rutl...@arm.com> Cc: Russell King <li...@armlinux.org.uk> Cc: devicet...@vger.kernel.org Cc: linux-arm-ker...@lists.infradead.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Tom Rini <tr...@konsulko.com> --- This patch takes the path that Rob e

[PATCH] ARM: dts: TI: Enable __symbols__ in dtb files for some platforms

when OF_OVERLAY is enabled. Cc: Jason Kridner Cc: Drew Fustini Cc: Robert Nelson Cc: Lokesh Vutla Cc: Frank Rowand Cc: Rob Herring Cc: Mark Rutland Cc: Russell King Cc: devicet...@vger.kernel.org Cc: linux-arm-ker...@lists.infradead.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Tom

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Wed, Aug 16, 2017 at 10:43:16AM -0500, Rob Herring wrote: > On Tue, Aug 15, 2017 at 5:49 PM, Tom Rini <tr...@konsulko.com> wrote: > > On Tue, Aug 15, 2017 at 05:36:11PM -0500, Rob Herring wrote: > >> On Tue, Aug 15, 2017 at 4:15 PM, Tom Rini <tr...@konsulko.com&

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Wed, Aug 16, 2017 at 10:43:16AM -0500, Rob Herring wrote: > On Tue, Aug 15, 2017 at 5:49 PM, Tom Rini wrote: > > On Tue, Aug 15, 2017 at 05:36:11PM -0500, Rob Herring wrote: > >> On Tue, Aug 15, 2017 at 4:15 PM, Tom Rini wrote: > >> > With support for stacked

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Wed, Aug 16, 2017 at 10:22:03AM -0500, Rob Herring wrote: > On Tue, Aug 15, 2017 at 7:42 PM, Tom Rini <tr...@konsulko.com> wrote: > > On Tue, Aug 15, 2017 at 04:50:40PM -0700, Frank Rowand wrote: > >> On 08/15/17 14:15, Tom Rini wrote: > >> > With sup

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Wed, Aug 16, 2017 at 10:22:03AM -0500, Rob Herring wrote: > On Tue, Aug 15, 2017 at 7:42 PM, Tom Rini wrote: > > On Tue, Aug 15, 2017 at 04:50:40PM -0700, Frank Rowand wrote: > >> On 08/15/17 14:15, Tom Rini wrote: > >> > With support for stacked overlays

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Tue, Aug 15, 2017 at 08:22:01PM -0700, Frank Rowand wrote: > On 08/15/17 17:42, Tom Rini wrote: > > On Tue, Aug 15, 2017 at 04:50:40PM -0700, Frank Rowand wrote: > >> On 08/15/17 14:15, Tom Rini wrote: > >>> With support for stacked overlays being part of l

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Tue, Aug 15, 2017 at 08:22:01PM -0700, Frank Rowand wrote: > On 08/15/17 17:42, Tom Rini wrote: > > On Tue, Aug 15, 2017 at 04:50:40PM -0700, Frank Rowand wrote: > >> On 08/15/17 14:15, Tom Rini wrote: > >>> With support for stacked overlays being part of l

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Tue, Aug 15, 2017 at 04:50:40PM -0700, Frank Rowand wrote: > On 08/15/17 14:15, Tom Rini wrote: > > With support for stacked overlays being part of libfdt it is now > > possible and likely that overlays which require __symbols__ will be > > applied to the dtb files ge

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Tue, Aug 15, 2017 at 04:50:40PM -0700, Frank Rowand wrote: > On 08/15/17 14:15, Tom Rini wrote: > > With support for stacked overlays being part of libfdt it is now > > possible and likely that overlays which require __symbols__ will be > > applied to the dtb files ge

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Tue, Aug 15, 2017 at 05:36:11PM -0500, Rob Herring wrote: > On Tue, Aug 15, 2017 at 4:15 PM, Tom Rini <tr...@konsulko.com> wrote: > > With support for stacked overlays being part of libfdt it is now > > possible and likely that overlays which require __symbols__ will be &

Re: [PATCH] devicetree: Enable generation of __symbols__ in all dtb files

On Tue, Aug 15, 2017 at 05:36:11PM -0500, Rob Herring wrote: > On Tue, Aug 15, 2017 at 4:15 PM, Tom Rini wrote: > > With support for stacked overlays being part of libfdt it is now > > possible and likely that overlays which require __symbols__ will be > > applied to th

[PATCH] devicetree: Enable generation of __symbols__ in all dtb files

.@konsulko.com> Cc: devicet...@vger.kernel.org Cc: linux-kernel@vger.kernel.org CC: linux-kbu...@vger.kernel.org Signed-off-by: Tom Rini <tr...@konsulko.com> --- In order for a dtb file to be useful with all types of overlays, it needs to be generated with the -@ flag passed to d

[PATCH] devicetree: Enable generation of __symbols__ in all dtb files

on the number of __symbol__ entries added to match the contents of the dts. Cc: Rob Herring Cc: Frank Rowand Cc: Masahiro Yamada Cc: Michal Marek Cc: Pantelis Antoniou Cc: devicet...@vger.kernel.org Cc: linux-kernel@vger.kernel.org CC: linux-kbu...@vger.kernel.org Signed-off-by: Tom Rini --- In order

[PATCH] dt-bindings: mtd: elm: Correct compatible string requirement

mail.com> Cc: Boris Brezillon <boris.brezil...@free-electrons.com> Cc: Marek Vasut <marek.va...@gmail.com> Cc: Richard Weinberger <rich...@nod.at> Cc: Cyrille Pitchen <cyrille.pitc...@wedev4u.fr> Cc: Rob Herring <robh...@kernel.org> Cc: Mark Rutland <mark.rutl...@arm.com&g

[PATCH] dt-bindings: mtd: elm: Correct compatible string requirement

Cc: Cyrille Pitchen Cc: Rob Herring Cc: Mark Rutland Signed-off-by: Tom Rini --- I have submitted a separate patch that correct the dm816x.dtsi to set the compatible string there for the elm from ti,816-elm to ti,am3352-elm and tested it on the hardware, where it works. It is quite likely

[PATCH] dt-bindings: gpmc: Correct location of generic gpmc binding

is Brezillon <boris.brezil...@free-electrons.com> Cc: Marek Vasut <marek.va...@gmail.com> Cc: Richard Weinberger <rich...@nod.at> Cc: Cyrille Pitchen <cyrille.pitc...@wedev4u.fr> Cc: Rob Herring <robh...@kernel.org> Cc: Mark Rutland <mark.rutl...@arm.com> Signed-off-by:

[PATCH] dt-bindings: gpmc: Correct location of generic gpmc binding

Cc: Rob Herring Cc: Mark Rutland Signed-off-by: Tom Rini --- Documentation/devicetree/bindings/mtd/gpmc-nand.txt| 2 +- Documentation/devicetree/bindings/mtd/gpmc-nor.txt | 4 ++-- Documentation/devicetree/bindings/mtd/gpmc-onenand.txt | 2 +- Documentation/devicetree/bindings/net/gpmc

[PATCH 2/2] ARM: dts: dm816x: Correct the state of the write protect pin

h...@kernel.org> Cc: Mark Rutland <mark.rutl...@arm.com> Cc: Russell King <li...@armlinux.org.uk> Cc: Tony Lindgren <t...@atomide.com> Signed-off-by: Mihail Grigorov <michael.grigo...@konsulko.com> Signed-off-by: Tom Rini <tr...@konsulko.com> --- arch/arm/boot/dts/dm81

[PATCH] multi_v7_defconfig: Enable OMAP MTD and DM816 AHCI

: Russell King <li...@armlinux.org.uk> Cc: Arnd Bergmann <a...@arndb.de> Cc: Tony Lindgren <t...@atomide.com> Cc: Mihail Grigorov <michael.grigo...@konsulko.com> Signed-off-by: Tom Rini <tr...@konsulko.com> --- arch/arm/configs/multi_v7_defconfig | 3 +++ 1 file change

[PATCH 2/2] ARM: dts: dm816x: Correct the state of the write protect pin

y Lindgren Signed-off-by: Mihail Grigorov Signed-off-by: Tom Rini --- arch/arm/boot/dts/dm8168-evm.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/dm8168-evm.dts b/arch/arm/boot/dts/dm8168-evm.dts index 996eba0c2e7a..c72a2132aa82 100644 --- a/arch/arm/boot/

[PATCH] multi_v7_defconfig: Enable OMAP MTD and DM816 AHCI

: Russell King Cc: Arnd Bergmann Cc: Tony Lindgren Cc: Mihail Grigorov Signed-off-by: Tom Rini --- arch/arm/configs/multi_v7_defconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 2685e03600b1..69b0b3c0fb6c

[PATCH 1/2] ARM: dts: dm816x: Correct NAND support nodes

<michael.grigo...@konsulko.com> Signed-off-by: Tom Rini <tr...@konsulko.com> --- arch/arm/boot/dts/dm8168-evm.dts | 32 arch/arm/boot/dts/dm816x.dtsi| 2 +- 2 files changed, 33 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/dm8168-evm.dt

[PATCH 1/2] ARM: dts: dm816x: Correct NAND support nodes

that we do not try and probe NAND before we probe the ELM. Cc: Rob Herring Cc: Mark Rutland Cc: Russell King Cc: Roger Quadros Cc: Tony Lindgren Cc: Mihail Grigorov Signed-off-by: Tom Rini --- arch/arm/boot/dts/dm8168-evm.dts | 32 arch/arm/boot/dts

Re: kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path

On Wed, Mar 15, 2017 at 04:03:44PM +0100, Michal Marek wrote: > Dne 15.3.2017 v 15:51 Tom Rini napsal(a): > > I found https://patchwork.kernel.org/patch/9442211/ today and I see that > > it was brought up again just before I sent my patch. I just want to > > point out that 94

Re: kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path

On Wed, Mar 15, 2017 at 04:03:44PM +0100, Michal Marek wrote: > Dne 15.3.2017 v 15:51 Tom Rini napsal(a): > > I found https://patchwork.kernel.org/patch/9442211/ today and I see that > > it was brought up again just before I sent my patch. I just want to > > point out that 94

Re: kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path

On Sat, Mar 11, 2017 at 11:59:22PM +, Tom Rini wrote: > On some architectures, such as arm64, KBUILD_IMAGE is not a full path > but instead just the build target. The builddeb script handles this > case correctly today and will try arch/$ARCH/boot/$KBUILD_IMAGE so we > can

Re: kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path

On Sat, Mar 11, 2017 at 11:59:22PM +, Tom Rini wrote: > On some architectures, such as arm64, KBUILD_IMAGE is not a full path > but instead just the build target. The builddeb script handles this > case correctly today and will try arch/$ARCH/boot/$KBUILD_IMAGE so we > can

[PATCH] kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path

<mma...@suse.com> Cc: linux-kbu...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc: Catalin Marinas <catalin.mari...@arm.com> Cc: Will Deacon <will.dea...@arm.com> Signed-off-by: Tom Rini <tr...@konsulko.com> --- It is currently a mixed-bag on if architectures will use a

[PATCH] kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path

Cc: linux-kbu...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc: Catalin Marinas Cc: Will Deacon Signed-off-by: Tom Rini --- It is currently a mixed-bag on if architectures will use a build target (arm, arm64, arc are certainly by inspection and a few others 'may') or a full path (x86

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Mon, Sep 12, 2016 at 03:46:23PM +0200, Matthijs van Duin wrote: > On 12 September 2016 at 15:35, Tom Rini <tr...@konsulko.com> wrote: > > What do you mean by "you can't put it to good use" ? Is that the case > > of stuff that's say exposed via a header

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Mon, Sep 12, 2016 at 03:46:23PM +0200, Matthijs van Duin wrote: > On 12 September 2016 at 15:35, Tom Rini wrote: > > What do you mean by "you can't put it to good use" ? Is that the case > > of stuff that's say exposed via a header and could be used but isn't (ie

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Sat, Sep 10, 2016 at 03:11:17AM +0200, Matthijs van Duin wrote: [snip] > On 8 September 2016 at 16:20, Nishanth Menon wrote: > > Minor point here > > It's not minor, it's quite crucial. > > > maintaining dts per paper spin is just too impossible to maintain > > Even if the

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Sat, Sep 10, 2016 at 03:11:17AM +0200, Matthijs van Duin wrote: [snip] > On 8 September 2016 at 16:20, Nishanth Menon wrote: > > Minor point here > > It's not minor, it's quite crucial. > > > maintaining dts per paper spin is just too impossible to maintain > > Even if the per-spin dtsi

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Sat, Sep 10, 2016 at 03:11:17AM +0200, Matthijs van Duin wrote: > On 8 September 2016 at 15:38, Rob Herring wrote: > > Yes, in theory a device can go from disabled to okay, but that's > > generally never been supported. Linux takes the simple approach of > > "disabled"

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Sat, Sep 10, 2016 at 03:11:17AM +0200, Matthijs van Duin wrote: > On 8 September 2016 at 15:38, Rob Herring wrote: > > Yes, in theory a device can go from disabled to okay, but that's > > generally never been supported. Linux takes the simple approach of > > "disabled" means ignore it. I think

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Thu, Sep 08, 2016 at 09:43:03PM -0500, Rob Herring wrote: > On Thu, Sep 8, 2016 at 2:05 PM, Frank Rowand wrote: > > On 09/08/16 06:38, Rob Herring wrote: > >> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: > >>> * Frank Rowand

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Thu, Sep 08, 2016 at 09:43:03PM -0500, Rob Herring wrote: > On Thu, Sep 8, 2016 at 2:05 PM, Frank Rowand wrote: > > On 09/08/16 06:38, Rob Herring wrote: > >> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: > >>> * Frank Rowand [160831 13:51]: [snip] > Why not just create a new

Re: [PATCH v2 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver

dule license and Chromium OS >Git history > ] > Signed-off-by: John Keeping <j...@metanate.com> > Tested-by: Genki Marshall <ge...@genki.is> Tested-by: Tom Rini <tr...@konsulko.com> -- Tom signature.asc Description: Digital signature

Re: [PATCH v2 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver

> Signed-off-by: John Keeping > Tested-by: Genki Marshall Tested-by: Tom Rini -- Tom signature.asc Description: Digital signature

Re: [PATCH v2 1/2] ASoC: rt5677: Add ACPI support

GPIOs are only available by index, so we need to register a > mapping to allow machine drivers to access the GPIOs by name. > > Signed-off-by: John Keeping <j...@metanate.com> Tested-by: Tom Rini <tr...@konsulko.com> -- Tom signature.asc Description: Digital signature

Re: [PATCH v2 1/2] ASoC: rt5677: Add ACPI support

GPIOs are only available by index, so we need to register a > mapping to allow machine drivers to access the GPIOs by name. > > Signed-off-by: John Keeping Tested-by: Tom Rini -- Tom signature.asc Description: Digital signature

Re: [U-Boot] Sharing code between Linux and bootloader (U-boot) ?

On Fri, May 20, 2016 at 04:28:23PM +0200, Sebastian Frias wrote: > Hi, > > Some bootloaders (like U-boot) support several HW devices: serial, > network, NAND, USB, etc. most of which are also supported by Linux. > > So the question is: is code shared? I mean, I understand that the > drivers

Re: [U-Boot] Sharing code between Linux and bootloader (U-boot) ?

On Fri, May 20, 2016 at 04:28:23PM +0200, Sebastian Frias wrote: > Hi, > > Some bootloaders (like U-boot) support several HW devices: serial, > network, NAND, USB, etc. most of which are also supported by Linux. > > So the question is: is code shared? I mean, I understand that the > drivers

Re: [PATCH] of: Add generic handling for hardware incomplete fail state

On Tue, Apr 12, 2016 at 03:27:32PM -0700, Tony Lindgren wrote: > * Rob Herring [160412 15:22]: > > On Tue, Apr 12, 2016 at 4:41 PM, Frank Rowand > > wrote: > > >>> Status of "fail-sss" is meant to indicate an error was detected in > > >>> the device,

Re: [PATCH] of: Add generic handling for hardware incomplete fail state

On Tue, Apr 12, 2016 at 03:27:32PM -0700, Tony Lindgren wrote: > * Rob Herring [160412 15:22]: > > On Tue, Apr 12, 2016 at 4:41 PM, Frank Rowand > > wrote: > > >>> Status of "fail-sss" is meant to indicate an error was detected in > > >>> the device, and that the error might (or might not) be

Re: [PATCH] of: Add generic handling for hardware incomplete fail state

On Tue, Apr 12, 2016 at 03:39:30PM -0700, Frank Rowand wrote: > On 4/12/2016 1:13 PM, Frank Rowand wrote: > > Hi Tony, > > < snip > > > > With that change, the bulk of your patch looks good, with > > minor changes: > > > > __of_device_is_available() would not need to change. > > > >

Re: [PATCH] of: Add generic handling for hardware incomplete fail state

On Tue, Apr 12, 2016 at 03:39:30PM -0700, Frank Rowand wrote: > On 4/12/2016 1:13 PM, Frank Rowand wrote: > > Hi Tony, > > < snip > > > > With that change, the bulk of your patch looks good, with > > minor changes: > > > > __of_device_is_available() would not need to change. > > > >

Re: [PATCH] Revert "Input: atmel_mxt_ts - disable interrupt for 50ms after reset"

On Fri, Apr 08, 2016 at 10:30:02PM +0100, Nick Dyer wrote: > On 2016-04-08 13:39, Tom Rini wrote: > >>>> I have a Pixel 2 here - can you advise how to reproduce? > >>> > >>> I (and a bunch of other folks, the linux-samus people now point people > >&g

Re: [PATCH] Revert "Input: atmel_mxt_ts - disable interrupt for 50ms after reset"

On Fri, Apr 08, 2016 at 10:30:02PM +0100, Nick Dyer wrote: > On 2016-04-08 13:39, Tom Rini wrote: > >>>> I have a Pixel 2 here - can you advise how to reproduce? > >>> > >>> I (and a bunch of other folks, the linux-samus people now point people > >&g

Re: [PATCH] Revert "Input: atmel_mxt_ts - disable interrupt for 50ms after reset"

On Fri, Apr 08, 2016 at 01:26:30PM +0100, Nick Dyer wrote: > On 2016-04-08 13:14, Tom Rini wrote: > > On Fri, Apr 08, 2016 at 10:10:06AM +0100, Nick Dyer wrote: > >> On 2016-04-07 23:52, Tom Rini wrote: > >>> This reverts commit 885f3fb9fa1f9e185e8a4e9051570874957

Re: [PATCH] Revert "Input: atmel_mxt_ts - disable interrupt for 50ms after reset"

On Fri, Apr 08, 2016 at 01:26:30PM +0100, Nick Dyer wrote: > On 2016-04-08 13:14, Tom Rini wrote: > > On Fri, Apr 08, 2016 at 10:10:06AM +0100, Nick Dyer wrote: > >> On 2016-04-07 23:52, Tom Rini wrote: > >>> This reverts commit 885f3fb9fa1f9e185e8a4e9051570874957

Re: [PATCH] Revert "Input: atmel_mxt_ts - disable interrupt for 50ms after reset"

On Fri, Apr 08, 2016 at 10:10:06AM +0100, Nick Dyer wrote: > On 2016-04-07 23:52, Tom Rini wrote: > > This reverts commit 885f3fb9fa1f9e185e8a4e905157087495734349 due to this > > change breaking the touchpad on the Chromebook Pixel 2015 on resume from > > sleep or warm rese

  1   2   3   4   5   6   >