On Fri, Oct 21, 2016 at 08:19:03PM +0200, Daniel Vetter wrote:
> On Fri, Oct 21, 2016 at 01:57:28PM +0100, Chris Wilson wrote:
> > I think of a use for sending an empty clip: where you don't want to
> > push any new pixel data, but you do want to be sure that the pipeline
> > has been flushed.
>
On Tue, Oct 18, 2016 at 10:54:49PM +0200, Richard Weinberger wrote:
> Most likely a copy error from the f2fs import.
>
> Signed-off-by: Richard Weinberger
> ---
> fs/crypto/crypto.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
On Thu, Oct 20, 2016 at 04:23:32PM -0700, Andy Lutomirski wrote:
> On Thu, Oct 20, 2016 at 4:03 PM, Dave Jones wrote:
> > On Thu, Oct 20, 2016 at 04:01:12PM -0700, Andy Lutomirski wrote:
> > > On Thu, Oct 20, 2016 at 3:50 PM, Dave Jones
> >
On Thu, Oct 20, 2016 at 04:23:32PM -0700, Andy Lutomirski wrote:
> On Thu, Oct 20, 2016 at 4:03 PM, Dave Jones wrote:
> > On Thu, Oct 20, 2016 at 04:01:12PM -0700, Andy Lutomirski wrote:
> > > On Thu, Oct 20, 2016 at 3:50 PM, Dave Jones
> > wrote:
> > > > On Tue, Oct 18, 2016 at
On 10/20/2016 5:43 PM, Chen Yu wrote:
> On 2016/10/19 6:21, John Youn wrote:
>> On 10/16/2016 7:42 PM, Chen Yu wrote:
>>>
>>>
>>> On 2016/10/15 3:37, John Youn wrote:
On 10/13/2016 4:36 PM, John Stultz wrote:
> From: Chen Yu
>
> The Hi6220's usb controller is
On Tue, Oct 18, 2016 at 10:54:48PM +0200, Richard Weinberger wrote:
> The operations supports both encryption and decryption.
>
> Signed-off-by: Richard Weinberger
> ---
> fs/crypto/crypto.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git
On 10/20/2016 5:43 PM, Chen Yu wrote:
> On 2016/10/19 6:21, John Youn wrote:
>> On 10/16/2016 7:42 PM, Chen Yu wrote:
>>>
>>>
>>> On 2016/10/15 3:37, John Youn wrote:
On 10/13/2016 4:36 PM, John Stultz wrote:
> From: Chen Yu
>
> The Hi6220's usb controller is limited in that it
On Tue, Oct 18, 2016 at 10:54:48PM +0200, Richard Weinberger wrote:
> The operations supports both encryption and decryption.
>
> Signed-off-by: Richard Weinberger
> ---
> fs/crypto/crypto.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/crypto/crypto.c
On Fri, 21 Oct 2016, Mason wrote:
> On 21/10/2016 21:14, Marc Zyngier wrote:
> > If connecting a device that signals its interrupt as level low to an
> > input line configured as level high doesn't strike you as a major
> > issue, nothing will. At that point, you can put anything you want in
> >
On Fri, 21 Oct 2016, Mason wrote:
> On 21/10/2016 21:14, Marc Zyngier wrote:
> > If connecting a device that signals its interrupt as level low to an
> > input line configured as level high doesn't strike you as a major
> > issue, nothing will. At that point, you can put anything you want in
> >
Hi,
On 10/21/2016 01:48 PM, Kevin Hilman wrote:
Dave Gerlach writes:
Add a generic power domain implementation, TI SCI PM Domains, that
will hook into the genpd framework and allow the TI SCI protocol to
control device power states.
Also, provide macros representing each
Hi,
On 10/21/2016 01:48 PM, Kevin Hilman wrote:
Dave Gerlach writes:
Add a generic power domain implementation, TI SCI PM Domains, that
will hook into the genpd framework and allow the TI SCI protocol to
control device power states.
Also, provide macros representing each device index as
On Fri, 21 Oct 2016, Michal Necasek wrote:
> I'll get back to you on whether increasing the timeout helps, it'll take
> a bit of testing. Does it actually sound plausible that some controllers
> could not get things done in 250ms but could in 275ms?
There is a bug in the new timer wheel code,
On Fri, 21 Oct 2016, Michal Necasek wrote:
> I'll get back to you on whether increasing the timeout helps, it'll take
> a bit of testing. Does it actually sound plausible that some controllers
> could not get things done in 250ms but could in 275ms?
There is a bug in the new timer wheel code,
On 21/10/2016 21:14, Marc Zyngier wrote:
> Mason wrote:
>
>> On 21/10/2016 19:46, Marc Zyngier wrote:
>>
>>> On 21/10/16 17:37, Mason wrote:
>>>
On my platform, one HW block pulls the interrupt line high
as long as it remains idle, and low when it is busy.
The device tree
On 21/10/2016 21:14, Marc Zyngier wrote:
> Mason wrote:
>
>> On 21/10/2016 19:46, Marc Zyngier wrote:
>>
>>> On 21/10/16 17:37, Mason wrote:
>>>
On my platform, one HW block pulls the interrupt line high
as long as it remains idle, and low when it is busy.
The device tree
On Fri, Oct 21, 2016 at 10:25:21AM -0700, Dave Hansen wrote:
> On 10/20/2016 11:24 PM, Liang Li wrote:
> > Dave Hansen suggested a new scheme to encode the data structure,
> > because of additional complexity, it's not implemented in v3.
>
> So, what do you want done with this patch set? Do you
On Fri, Oct 21, 2016 at 10:25:21AM -0700, Dave Hansen wrote:
> On 10/20/2016 11:24 PM, Liang Li wrote:
> > Dave Hansen suggested a new scheme to encode the data structure,
> > because of additional complexity, it's not implemented in v3.
>
> So, what do you want done with this patch set? Do you
Hi,
I generated a solution with tools/power/acpi makefiles.
Please give it a try.
Sorry for the hackish build includes.
Thanks and best regards
Lv
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Zheng,
> Lv
> Subject: RE: [PATCH] ACPICA: arm64:
Hi,
I generated a solution with tools/power/acpi makefiles.
Please give it a try.
Sorry for the hackish build includes.
Thanks and best regards
Lv
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Zheng,
> Lv
> Subject: RE: [PATCH] ACPICA: arm64:
Alan,
I'll get back to you on whether increasing the timeout helps, it'll take a bit
of testing. Does it actually sound plausible that some controllers could not
get things done in 250ms but could in 275ms?
I will note that according to the table in <1>, a 250ms timeout with a HZ=250
Alan,
I'll get back to you on whether increasing the timeout helps, it'll take a bit
of testing. Does it actually sound plausible that some controllers could not
get things done in 250ms but could in 275ms?
I will note that according to the table in <1>, a 250ms timeout with a HZ=250
Andrei Vagin writes:
>> Barring some stupid mistake this looks like it fixes both the performance
>> and the correctness issues I was able to spot earlier. Andrei if you
>> could give this version a look over I would appreciate it.
>
> Eric, could you try out this script:
Andrei Vagin writes:
>> Barring some stupid mistake this looks like it fixes both the performance
>> and the correctness issues I was able to spot earlier. Andrei if you
>> could give this version a look over I would appreciate it.
>
> Eric, could you try out this script:
[snip script]
> It
On 10/20/2016 11:38 AM, Randy Li wrote:
> On the rk3288 USB host-only port (the one that's not the OTG-enabled
> port) the PHY can get into a bad state when a wakeup is asserted (not
> just a wakeup from full system suspend but also a wakeup from
> autosuspend).
>
> We can get the PHY out of its
On 10/20/2016 11:38 AM, Randy Li wrote:
> On the rk3288 USB host-only port (the one that's not the OTG-enabled
> port) the PHY can get into a bad state when a wakeup is asserted (not
> just a wakeup from full system suspend but also a wakeup from
> autosuspend).
>
> We can get the PHY out of its
ee it's been merged here now:
https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/commit/?h=perf/c2c=5a1a99cd2e4e15571a74f65facf05f806d5303fd
and the updated perf-c2c-for-mingo-20161021 works, so thanks all.
Kim
ffdb4c) at perf.c:466
> > #8 main (argc=2, argv=0x7fffddb0) at perf.c:610
> > (gdb)
> >
> > All the above work fine when run under sudo.
>
> ugh, stupid mistake.. attached patch fixes that for me
I see it's been merged here now:
https://git.kernel.org/cgit/linu
On Fri, 21 Oct 2016 11:11:14 -0400 Don Zickus wrote:
> On Thu, Oct 20, 2016 at 08:25:27PM -0700, Andrew Morton wrote:
> > On Thu, 20 Oct 2016 12:14:14 -0400 Don Zickus wrote:
> >
> > > > > -static int watchdog_nmi_enable(unsigned int cpu) { return 0; }
>
On Fri, 21 Oct 2016 11:11:14 -0400 Don Zickus wrote:
> On Thu, Oct 20, 2016 at 08:25:27PM -0700, Andrew Morton wrote:
> > On Thu, 20 Oct 2016 12:14:14 -0400 Don Zickus wrote:
> >
> > > > > -static int watchdog_nmi_enable(unsigned int cpu) { return 0; }
> > > > > -static void
On Fri, Oct 21, 2016 at 11:17:23AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.8.4 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Fri, Oct 21, 2016 at 11:17:23AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.8.4 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Fri, Oct 21, 2016 at 11:17:20AM +0200, Greg Kroah-Hartman wrote:
>
> NOTE, this will be the last 4.7.y kernel to be released. After this
> one, the 4.7.y series is end-of-life. You should be moving to the 4.8.y
> kernel series at this point in time.
>
On Fri, Oct 21, 2016 at 11:17:20AM +0200, Greg Kroah-Hartman wrote:
>
> NOTE, this will be the last 4.7.y kernel to be released. After this
> one, the 4.7.y series is end-of-life. You should be moving to the 4.8.y
> kernel series at this point in time.
>
On 10/21/2016 02:02 PM, Santosh Shilimkar wrote:
On 10/21/2016 12:00 PM, Kevin Hilman wrote:
Dave Gerlach writes:
[...]
BTW, what is the the status of the TI-SCI protocol drivers themselves?
This can't be merged until that is or this won't even compile.
I was just
On 10/21/2016 02:02 PM, Santosh Shilimkar wrote:
On 10/21/2016 12:00 PM, Kevin Hilman wrote:
Dave Gerlach writes:
[...]
BTW, what is the the status of the TI-SCI protocol drivers themselves?
This can't be merged until that is or this won't even compile.
I was just about to ask the same
On Fri, Oct 21, 2016 at 11:15:51AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.27 release.
> There are 25 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Oct 21, 2016 at 11:15:51AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.27 release.
> There are 25 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, 21 Oct 2016 20:39:41 +0200
Mason wrote:
> On 21/10/2016 19:46, Marc Zyngier wrote:
>
> > On 21/10/16 17:37, Mason wrote:
> >
> >> On my platform, one HW block pulls the interrupt line high
> >> as long as it remains idle, and low when it is busy.
> >>
> >> The
On Fri, 21 Oct 2016 20:39:41 +0200
Mason wrote:
> On 21/10/2016 19:46, Marc Zyngier wrote:
>
> > On 21/10/16 17:37, Mason wrote:
> >
> >> On my platform, one HW block pulls the interrupt line high
> >> as long as it remains idle, and low when it is busy.
> >>
> >> The device tree node is:
>
David Lechner writes:
> This adds a device tree definition file for LEGO MINDSTORMS EV3.
>
> What is working:
>
> * Pin muxing
> * MicroSD card reader
> * UART on input port 1
>
> What is partially working:
>
> * Buttons - working after GPIO fix
> * LEDs - working after
David Lechner writes:
> This adds a device tree definition file for LEGO MINDSTORMS EV3.
>
> What is working:
>
> * Pin muxing
> * MicroSD card reader
> * UART on input port 1
>
> What is partially working:
>
> * Buttons - working after GPIO fix
> * LEDs - working after GPIO fix
> *
On Fri, Oct 21, 2016 at 7:37 PM, Sinan Kaya wrote:
> The interrupts can now be delivered as platform MSI interrupts on newer
> platforms. The code looks for a new OF and ACPI strings in order to enable
> the functionality.
> +#ifdef CONFIG_GENERIC_MSI_IRQ_DOMAIN
> +static
On Fri, Oct 21, 2016 at 7:37 PM, Sinan Kaya wrote:
> The interrupts can now be delivered as platform MSI interrupts on newer
> platforms. The code looks for a new OF and ACPI strings in order to enable
> the functionality.
> +#ifdef CONFIG_GENERIC_MSI_IRQ_DOMAIN
> +static void
Linus,
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
Linus,
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
On Fri, Oct 21, 2016 at 09:27:10PM +0300, Krzysztof Kozlowski wrote:
>
> I acked this twice (v1 and v2)... and still you are ignoring them. I am
> sorry, I am not gonna to ack this third time!
>
> For v2 I acked also other patches but it it is not there as well...
>
> BR,
> Krzysztof
I'm
On Fri, Oct 21, 2016 at 09:27:10PM +0300, Krzysztof Kozlowski wrote:
>
> I acked this twice (v1 and v2)... and still you are ignoring them. I am
> sorry, I am not gonna to ack this third time!
>
> For v2 I acked also other patches but it it is not there as well...
>
> BR,
> Krzysztof
I'm
On Thu, 2016-10-20 at 13:16 +, Eugeniy Paltsev wrote:
> On Thu, 2016-10-20 at 13:48 +0300, Andy Shevchenko wrote:
> > On Thu, 2016-09-15 at 16:14 +0300, Eugeniy Paltsev wrote:
> > >
> > > This patch is to address a proposal by Andy in this thread:
> > >
On Thu, 2016-10-20 at 13:16 +, Eugeniy Paltsev wrote:
> On Thu, 2016-10-20 at 13:48 +0300, Andy Shevchenko wrote:
> > On Thu, 2016-09-15 at 16:14 +0300, Eugeniy Paltsev wrote:
> > >
> > > This patch is to address a proposal by Andy in this thread:
> > >
On 10/21/2016 12:00 PM, Kevin Hilman wrote:
Dave Gerlach writes:
[...]
BTW, what is the the status of the TI-SCI protocol drivers themselves?
This can't be merged until that is or this won't even compile.
I was just about to ask the same question.
Regards,
Santosh
On 10/21/2016 12:00 PM, Kevin Hilman wrote:
Dave Gerlach writes:
[...]
BTW, what is the the status of the TI-SCI protocol drivers themselves?
This can't be merged until that is or this won't even compile.
I was just about to ask the same question.
Regards,
Santosh
Dave Gerlach writes:
> Introduce a ti_sci_pm_domains driver to act as a generic pm domain provider
> to allow each device to attach and associate it's ti-sci-id so that it can
> be controlled through the TI SCI protocol.
>
> This driver implements a simple genpd where each
Dave Gerlach writes:
> Introduce a ti_sci_pm_domains driver to act as a generic pm domain provider
> to allow each device to attach and associate it's ti-sci-id so that it can
> be controlled through the TI SCI protocol.
>
> This driver implements a simple genpd where each device node has
> a
On 10/21/2016 08:27 PM, Krzysztof Kozlowski wrote:
> On Thu, Oct 20, 2016 at 07:42:44PM -0200, Sergio Prado wrote:
>> Removing CONFIG_MTD_NAND_S3C2410_HWECC option and adding a ecc_mode
>> field in the drivers's platform data structure so it can be selectable
>> via platform data.
>>
>> Also
On 10/21/2016 08:27 PM, Krzysztof Kozlowski wrote:
> On Thu, Oct 20, 2016 at 07:42:44PM -0200, Sergio Prado wrote:
>> Removing CONFIG_MTD_NAND_S3C2410_HWECC option and adding a ecc_mode
>> field in the drivers's platform data structure so it can be selectable
>> via platform data.
>>
>> Also
Huge pages are detrimental for small file: they causes noticible
overhead on both allocation performance and memory footprint.
This patch aimed to address this issue by avoiding huge pages until file
grown to size of huge page. This would cover most of the cases where huge
pages causes
Huge pages are detrimental for small file: they causes noticible
overhead on both allocation performance and memory footprint.
This patch aimed to address this issue by avoiding huge pages until file
grown to size of huge page. This would cover most of the cases where huge
pages causes
> When the author of the semantic patch language is telling you to stand down,
The collaboration evolved between Julia and me during the years somehow.
Different software development opinions occur then as usual.
Further opinions from contributors like you can eventually show variations
between
> When the author of the semantic patch language is telling you to stand down,
The collaboration evolved between Julia and me during the years somehow.
Different software development opinions occur then as usual.
Further opinions from contributors like you can eventually show variations
between
Dave Gerlach writes:
> Add a generic power domain implementation, TI SCI PM Domains, that
> will hook into the genpd framework and allow the TI SCI protocol to
> control device power states.
>
> Also, provide macros representing each device index as understood
> by TI SCI to be
Dave Gerlach writes:
> Add a generic power domain implementation, TI SCI PM Domains, that
> will hook into the genpd framework and allow the TI SCI protocol to
> control device power states.
>
> Also, provide macros representing each device index as understood
> by TI SCI to be used in the
On 10/21/2016 11:37 AM, Eric W. Biederman wrote:
> David Miller writes:
>
>> From: ebied...@xmission.com (Eric W. Biederman)
>> Date: Fri, 21 Oct 2016 00:26:55 -0500
>>
>>> So as far as I can tell you are advocating for a change to support a
>>> driver doing something that
On 10/21/2016 11:37 AM, Eric W. Biederman wrote:
> David Miller writes:
>
>> From: ebied...@xmission.com (Eric W. Biederman)
>> Date: Fri, 21 Oct 2016 00:26:55 -0500
>>
>>> So as far as I can tell you are advocating for a change to support a
>>> driver doing something that is completely
On Fri, Oct 21, 2016 at 01:36:52PM -0500, David Lechner wrote:
> This patch series adds support for LEGO MINDSTORTMS EV3[1]. This is a TI
> AM1808
> based board.
>
> This patch series has been tested working (along with some hacks to fix the
> GPIOs) on an EV3.
>
> There are still quite a few
On Fri, Oct 21, 2016 at 01:36:52PM -0500, David Lechner wrote:
> This patch series adds support for LEGO MINDSTORTMS EV3[1]. This is a TI
> AM1808
> based board.
>
> This patch series has been tested working (along with some hacks to fix the
> GPIOs) on an EV3.
>
> There are still quite a few
On Fri, Oct 21, 2016 at 02:48:35PM +0200, Richard Weinberger wrote:
> +
> + if (!dentry)
> + return ERR_PTR(-ECHILD);
> +
> + if (ubifs_crypt_is_encrypted(inode)) {
> + err = fscrypt_get_encryption_info(inode);
> + if (err)
> + return
On Fri, Oct 21, 2016 at 02:48:35PM +0200, Richard Weinberger wrote:
> +
> + if (!dentry)
> + return ERR_PTR(-ECHILD);
> +
> + if (ubifs_crypt_is_encrypted(inode)) {
> + err = fscrypt_get_encryption_info(inode);
> + if (err)
> + return
On Fri, 2016-10-21 at 13:03 -0500, Zach Brown wrote:
> Is there a way to get NAPI to poll all the time?
> Or just any way to get netdevices to use only polling and no interrupts?
>
> We have some rt targets where the jitter can be improved by disabling
> interrupts and using just polling. In
On Fri, 2016-10-21 at 13:03 -0500, Zach Brown wrote:
> Is there a way to get NAPI to poll all the time?
> Or just any way to get netdevices to use only polling and no interrupts?
>
> We have some rt targets where the jitter can be improved by disabling
> interrupts and using just polling. In
On Thu, Oct 20, 2016 at 04:28:01PM +, vad...@mellanox.com wrote:
> From: Vadim Pasternak
>
> Enable system support for the Mellanox Technologies hotplug platform
> driver, which provides support for the next Mellanox basic systems:
> "msx6710", "msx6720", "msb7700",
On Thu, Oct 20, 2016 at 04:28:01PM +, vad...@mellanox.com wrote:
> From: Vadim Pasternak
>
> Enable system support for the Mellanox Technologies hotplug platform
> driver, which provides support for the next Mellanox basic systems:
> "msx6710", "msx6720", "msb7700", "msn2700", "msx1410",
2016-10-21 11:27+, David Laight:
> From: Pan Xinhui
>> Sent: 20 October 2016 22:28
>> Commit ("x86, kvm: support vcpu preempted check") add one field "__u8
>> preempted" into struct kvm_steal_time. This field tells if one vcpu is
>> running or not.
>>
>> It is zero if 1) some old KVM deos not
2016-10-21 11:27+, David Laight:
> From: Pan Xinhui
>> Sent: 20 October 2016 22:28
>> Commit ("x86, kvm: support vcpu preempted check") add one field "__u8
>> preempted" into struct kvm_steal_time. This field tells if one vcpu is
>> running or not.
>>
>> It is zero if 1) some old KVM deos not
On 21/10/2016 19:46, Marc Zyngier wrote:
> On 21/10/16 17:37, Mason wrote:
>
>> On my platform, one HW block pulls the interrupt line high
>> as long as it remains idle, and low when it is busy.
>>
>> The device tree node is:
>>
>> test@2 {
>> compatible =
David Miller writes:
> From: ebied...@xmission.com (Eric W. Biederman)
> Date: Fri, 21 Oct 2016 00:26:55 -0500
>
>> So as far as I can tell you are advocating for a change to support a
>> driver doing something that is completely pointless. So no let's not
>> export this
On 21/10/2016 19:46, Marc Zyngier wrote:
> On 21/10/16 17:37, Mason wrote:
>
>> On my platform, one HW block pulls the interrupt line high
>> as long as it remains idle, and low when it is busy.
>>
>> The device tree node is:
>>
>> test@2 {
>> compatible =
David Miller writes:
> From: ebied...@xmission.com (Eric W. Biederman)
> Date: Fri, 21 Oct 2016 00:26:55 -0500
>
>> So as far as I can tell you are advocating for a change to support a
>> driver doing something that is completely pointless. So no let's not
>> export this symbol. Please fix the
This changes the davinci default configuration to compile the davinci
MMC driver into the kernel. This allows booting from an SD card without
requiring an initrd containing the kernel module.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 4 ++--
This changes the davinci default configuration to compile the davinci
MMC driver into the kernel. This allows booting from an SD card without
requiring an initrd containing the kernel module.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 4 ++--
1 file changed, 2
This patch series adds support for LEGO MINDSTORTMS EV3[1]. This is a TI AM1808
based board.
This patch series has been tested working (along with some hacks to fix the
GPIOs) on an EV3.
There are still quite a few additional new drivers that need to be submitted
to get everything working. This
The gpio-poweroff driver is needed by LEGO MINDSTORMS EV3 (AM1808 based
board).
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/davinci_all_defconfig
This adds a device tree definition file for LEGO MINDSTORMS EV3.
What is working:
* Pin muxing
* MicroSD card reader
* UART on input port 1
What is partially working:
* Buttons - working after GPIO fix
* LEDs - working after GPIO fix
* Poweroff/reset - working after GPIO fix
* Flash memory -
This patch series adds support for LEGO MINDSTORTMS EV3[1]. This is a TI AM1808
based board.
This patch series has been tested working (along with some hacks to fix the
GPIOs) on an EV3.
There are still quite a few additional new drivers that need to be submitted
to get everything working. This
The gpio-poweroff driver is needed by LEGO MINDSTORMS EV3 (AM1808 based
board).
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/davinci_all_defconfig
b/arch/arm/configs/davinci_all_defconfig
index
This adds a device tree definition file for LEGO MINDSTORMS EV3.
What is working:
* Pin muxing
* MicroSD card reader
* UART on input port 1
What is partially working:
* Buttons - working after GPIO fix
* LEDs - working after GPIO fix
* Poweroff/reset - working after GPIO fix
* Flash memory -
The LEDs default-on trigger is nice to have. For example, it can be used
to configure a LED as a power indicator.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
In the davinci default configuration, don't append the git revision to
the local kernel version by. This seems like the more desirable default
value.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
The LEDs default-on trigger is nice to have. For example, it can be used
to configure a LED as a power indicator.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/davinci_all_defconfig
In the davinci default configuration, don't append the git revision to
the local kernel version by. This seems like the more desirable default
value.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
On Oct 21, 2016, at 12:16 PM, Fabian Frederick wrote:
>
> This patch tries to address the following comment in ext4/resize.c
> "This could probably be made into a module, because it is not often in use."
>
> Having ext4 resizing in a module would give a lot of depmod
>
On Oct 21, 2016, at 12:16 PM, Fabian Frederick wrote:
>
> This patch tries to address the following comment in ext4/resize.c
> "This could probably be made into a module, because it is not often in use."
>
> Having ext4 resizing in a module would give a lot of depmod
> dependency cycles but we
On Fri, Oct 21, 2016 at 02:48:40PM +0200, Richard Weinberger wrote:
> @@ -190,6 +191,10 @@ long ubifs_ioctl(struct file *file, unsigned int cmd,
> unsigned long arg)
> sizeof(policy)))
> return -EFAULT;
>
> + err =
On Fri, Oct 21, 2016 at 02:48:40PM +0200, Richard Weinberger wrote:
> @@ -190,6 +191,10 @@ long ubifs_ioctl(struct file *file, unsigned int cmd,
> unsigned long arg)
> sizeof(policy)))
> return -EFAULT;
>
> + err =
On Thu, Oct 20, 2016 at 07:42:44PM -0200, Sergio Prado wrote:
> Removing CONFIG_MTD_NAND_S3C2410_HWECC option and adding a ecc_mode
> field in the drivers's platform data structure so it can be selectable
> via platform data.
>
> Also setting this field to NAND_ECC_SOFT in all boards using this
>
On Thu, Oct 20, 2016 at 07:42:44PM -0200, Sergio Prado wrote:
> Removing CONFIG_MTD_NAND_S3C2410_HWECC option and adding a ecc_mode
> field in the drivers's platform data structure so it can be selectable
> via platform data.
>
> Also setting this field to NAND_ECC_SOFT in all boards using this
>
On Fri, Oct 21, 2016 at 02:48:30PM +0200, Richard Weinberger wrote:
> +
> + if (ubifs_crypt_is_encrypted(inode)) {
> + int clen = le16_to_cpu(dn->compr_size);
> +
> + if (clen <= 0 || clen > UBIFS_BLOCK_SIZE || clen > dlen)
> + goto dump;
> +
> +
On Fri, Oct 21, 2016 at 02:48:30PM +0200, Richard Weinberger wrote:
> +
> + if (ubifs_crypt_is_encrypted(inode)) {
> + int clen = le16_to_cpu(dn->compr_size);
> +
> + if (clen <= 0 || clen > UBIFS_BLOCK_SIZE || clen > dlen)
> + goto dump;
> +
> +
On Thu, 2016-10-20 at 16:31 -0700, Chris Healy wrote:
> As a little background, in the case Nick is referring to with the
> S7813, it was actually with a stock Synaptics Eval Board and stock
> Firmware provided by Synaptics.
>
> Not sure if that is relevant or not.
Yes, it's quite relevant -
On Thu, 2016-10-20 at 16:31 -0700, Chris Healy wrote:
> As a little background, in the case Nick is referring to with the
> S7813, it was actually with a stock Synaptics Eval Board and stock
> Firmware provided by Synaptics.
>
> Not sure if that is relevant or not.
Yes, it's quite relevant -
301 - 400 of 1918 matches
Mail list logo