There are some comments which can be updated for better readability of
the driver. Update abbreviations to capital letters in the comments.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 98 ++--
1 file changed, 48 insertions(+), 50
There are some comments which can be updated for better readability of
the driver. Update abbreviations to capital letters in the comments.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 98 ++--
1 file changed, 48 insertions(+), 50
Add macro defines for ZynqMP DDR controller. These macros will be used
for ZynqMP ECC operations.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 168 +++
1 file changed, 168 insertions(+)
diff --git a/drivers/edac/synopsys_edac.c
Add macro defines for ZynqMP DDR controller. These macros will be used
for ZynqMP ECC operations.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 168 +++
1 file changed, 168 insertions(+)
diff --git a/drivers/edac/synopsys_edac.c
Add information of ZynqMP DDRC which reports the single bit errors that
are corrected and the double bit errors that are detected.
Signed-off-by: Manish Narani
Reviewed-by: Rob Herring
---
.../bindings/memory-controllers/synopsys.txt | 27 ++
1 file changed, 22
This patch series enhances the current EDAC driver to support different
platforms. This series adds support for ZynqMP DDRC controller in synopsys
EDAC driver. This series also adds Device tree properties and relevant
binding documentation.
Changes in v2:
- Moved checking of
Add information of ZynqMP DDRC which reports the single bit errors that
are corrected and the double bit errors that are detected.
Signed-off-by: Manish Narani
Reviewed-by: Rob Herring
---
.../bindings/memory-controllers/synopsys.txt | 27 ++
1 file changed, 22
This patch series enhances the current EDAC driver to support different
platforms. This series adds support for ZynqMP DDRC controller in synopsys
EDAC driver. This series also adds Device tree properties and relevant
binding documentation.
Changes in v2:
- Moved checking of
Add EDAC ECC support for ZynqMP DDRC IP. The IP supports interrupts for
corrected and uncorrected errors. Add interrupt handlers for the same.
Signed-off-by: Manish Narani
---
drivers/edac/Kconfig | 2 +-
drivers/edac/synopsys_edac.c | 328 ---
Add EDAC ECC support for ZynqMP DDRC IP. The IP supports interrupts for
corrected and uncorrected errors. Add interrupt handlers for the same.
Signed-off-by: Manish Narani
---
drivers/edac/Kconfig | 2 +-
drivers/edac/synopsys_edac.c | 328 ---
Add support for Error Injection for ZynqMP DDRC IP. For injecting
errors, the Row, Column, Bank, Bank Group and Rank bits positions are
determined via Address Map registers of Synopsys DDRC.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 421
Add support for Error Injection for ZynqMP DDRC IP. For injecting
errors, the Row, Column, Bank, Bank Group and Rank bits positions are
determined via Address Map registers of Synopsys DDRC.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 421
The current driver has functions which are always returning 0. Those
functions can be modified to void.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 22 --
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/drivers/edac/synopsys_edac.c
Add platform specific structures, so that we can add different IP
support later using quirks.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 91 +++-
1 file changed, 65 insertions(+), 26 deletions(-)
diff --git
Add ddrc memory controller node in dts. The size mentioned in dts is
0x3, because we need to access DDR_QOS INTR registers located at
0xFD090208 from this driver.
Signed-off-by: Manish Narani
---
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git
The current driver has functions which are always returning 0. Those
functions can be modified to void.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 22 --
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/drivers/edac/synopsys_edac.c
Add platform specific structures, so that we can add different IP
support later using quirks.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 91 +++-
1 file changed, 65 insertions(+), 26 deletions(-)
diff --git
Add ddrc memory controller node in dts. The size mentioned in dts is
0x3, because we need to access DDR_QOS INTR registers located at
0xFD090208 from this driver.
Signed-off-by: Manish Narani
---
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git
Rename the static functions to a shorter name. Since this is Synopsys
EDAC driver, better to remove unnecessary 'synps_' prefix in function
names.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 56 ++--
1 file changed, 28 insertions(+),
Rename the static functions to a shorter name. Since this is Synopsys
EDAC driver, better to remove unnecessary 'synps_' prefix in function
names.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 56 ++--
1 file changed, 28 insertions(+),
Modify the driver with some changes for code clean up. Update the debug
messages for EDAC errors reported. Increase the indentation of the
macros for better readability.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 104 +--
1 file
Modify the driver with some changes for code clean up. Update the debug
messages for EDAC errors reported. Increase the indentation of the
macros for better readability.
Signed-off-by: Manish Narani
---
drivers/edac/synopsys_edac.c | 104 +--
1 file
On Thu, Oct 4, 2018 at 5:11 PM Timo Alho wrote:
> On 03.10.2018 11:26, Jonathan Hunter wrote:
> > On 02/10/18 22:21, Arnd Bergmann wrote:
> >> The newly added tegra_bpmp_resume function is unused when CONFIG_PM
> >> is disabled:
> >>
> >> drivers/firmware/tegra/bpmp.c:847:12: error:
On Thu, Oct 4, 2018 at 5:11 PM Timo Alho wrote:
> On 03.10.2018 11:26, Jonathan Hunter wrote:
> > On 02/10/18 22:21, Arnd Bergmann wrote:
> >> The newly added tegra_bpmp_resume function is unused when CONFIG_PM
> >> is disabled:
> >>
> >> drivers/firmware/tegra/bpmp.c:847:12: error:
Em Wed, Oct 03, 2018 at 07:57:12PM +0300, Alexey Budankov escreveu:
>
> Store -k clockid frequency into Perf trace to enable timestamps
> derived metrics conversion into wall clock time on reporting stage.
Humm, looking at where this is documented, we already have this in the
Em Wed, Oct 03, 2018 at 07:57:12PM +0300, Alexey Budankov escreveu:
>
> Store -k clockid frequency into Perf trace to enable timestamps
> derived metrics conversion into wall clock time on reporting stage.
Humm, looking at where this is documented, we already have this in the
On Thu, Oct 4, 2018 at 2:04 PM Daniel Lezcano wrote:
>
> The function get_loadavg() returns almost always zero. To be more
> precise, statistically speaking for a total of 1023379 times passing
> in the function, the load is equal to zero 1020728 times, greater than
> 100, 610 times, the
On Thu, Oct 4, 2018 at 2:04 PM Daniel Lezcano wrote:
>
> The function get_loadavg() returns almost always zero. To be more
> precise, statistically speaking for a total of 1023379 times passing
> in the function, the load is equal to zero 1020728 times, greater than
> 100, 610 times, the
The ARM Architecture Reference Manual allows for caches to be "invisible" and
thus not specified in the system registers under some scenarios such as if the
cache cannot be managed by set/way operations.
However, such caches may be specified in the ACPI PPTT table for workload
The ARM Architecture Reference Manual allows for caches to be "invisible" and
thus not specified in the system registers under some scenarios such as if the
cache cannot be managed by set/way operations.
However, such caches may be specified in the ACPI PPTT table for workload
If a cache has an unknown type because neither the hardware nor the
firmware told us, an entry in the sysfs tree will be made, but the type
file will not be present. lscpu depends on the type file being present
for every entry, and will error out without printing system information
if lscpu
The type of a cache might not be specified by architectural mechanisms (ie
system registers), but its type might be specified in the PPTT. In this
case, we should populate the type of the cache, rather than leave it
undefined.
This fixes the issue where the cacheinfo driver will not populate
If a cache has an unknown type because neither the hardware nor the
firmware told us, an entry in the sysfs tree will be made, but the type
file will not be present. lscpu depends on the type file being present
for every entry, and will error out without printing system information
if lscpu
The type of a cache might not be specified by architectural mechanisms (ie
system registers), but its type might be specified in the PPTT. In this
case, we should populate the type of the cache, rather than leave it
undefined.
This fixes the issue where the cacheinfo driver will not populate
On Thu, Oct 4, 2018 at 3:36 AM Viresh Kumar wrote:
>
> On 25-09-18, 14:43, Rob Herring wrote:
> > On Tue, Sep 25, 2018 at 5:25 AM Rajendra Nayak
> > wrote:
> > >
> > > Hi Rob,
> > >
> > > []...
> > > > + rpmhpd_opp_table: opp-table {
> > > > + compatible =
On Thu, Oct 4, 2018 at 3:36 AM Viresh Kumar wrote:
>
> On 25-09-18, 14:43, Rob Herring wrote:
> > On Tue, Sep 25, 2018 at 5:25 AM Rajendra Nayak
> > wrote:
> > >
> > > Hi Rob,
> > >
> > > []...
> > > > + rpmhpd_opp_table: opp-table {
> > > > + compatible =
Hi,
On Wed, Oct 3, 2018 at 5:14 PM Matthias Kaehlcke wrote:
>
> The node has a reg property, therefore its name should include a unit
> address.
>
> Also change the name from 'usb_id_nopull' to 'usb-id-nopull' to follow
> DT conventions.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> Changes in
Hi,
On Wed, Oct 3, 2018 at 5:14 PM Matthias Kaehlcke wrote:
>
> The node has a reg property, therefore its name should include a unit
> address.
>
> Also change the name from 'usb_id_nopull' to 'usb-id-nopull' to follow
> DT conventions.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> Changes in
On Wed, Oct 3, 2018 at 2:19 AM Masahiro Yamada
wrote:
>
> Enable the UniPhier SD controller driver.
>
> Signed-off-by: Masahiro Yamada
Applied to next/defconfig, thanks!
Note: I think it would actually be better to update both defconfig files in one
patch, since you are doing the same change
On Wed, Oct 3, 2018 at 2:19 AM Masahiro Yamada
wrote:
>
> Enable the UniPhier SD controller driver.
>
> Signed-off-by: Masahiro Yamada
Applied to next/defconfig, thanks!
Note: I think it would actually be better to update both defconfig files in one
patch, since you are doing the same change
On 03.10.2018 11:26, Jonathan Hunter wrote:
On 02/10/18 22:21, Arnd Bergmann wrote:
The newly added tegra_bpmp_resume function is unused when CONFIG_PM
is disabled:
drivers/firmware/tegra/bpmp.c:847:12: error: 'tegra_bpmp_resume' defined but
not used [-Werror=unused-function]
static int
On 03.10.2018 11:26, Jonathan Hunter wrote:
On 02/10/18 22:21, Arnd Bergmann wrote:
The newly added tegra_bpmp_resume function is unused when CONFIG_PM
is disabled:
drivers/firmware/tegra/bpmp.c:847:12: error: 'tegra_bpmp_resume' defined but
not used [-Werror=unused-function]
static int
On Wed, Oct 3, 2018 at 2:19 AM Masahiro Yamada
wrote:
>
> Enable the UniPhier SD controller driver.
>
> Signed-off-by: Masahiro Yamada
Applied to next/defconfig, thanks!
Arnd
On Wed, Oct 3, 2018 at 2:19 AM Masahiro Yamada
wrote:
>
> Enable the UniPhier SD controller driver.
>
> Signed-off-by: Masahiro Yamada
Applied to next/defconfig, thanks!
Arnd
On Thu, Oct 4, 2018 at 2:54 AM Masahiro Yamada
wrote:
> UniPhier ARM SoC DT updates for v4.20
>
> - Add more clocks to NAND controller nodes
>
> - Add SPI controller nodes
>
> - Add SD controller nodes
>
> - Add USB 3.0 and its PHY nodes
>
> - Add PHY nodes for USB 2.0
Pulled into next/dt,
On Thu, Oct 4, 2018 at 2:54 AM Masahiro Yamada
wrote:
> UniPhier ARM SoC DT updates for v4.20
>
> - Add more clocks to NAND controller nodes
>
> - Add SPI controller nodes
>
> - Add SD controller nodes
>
> - Add USB 3.0 and its PHY nodes
>
> - Add PHY nodes for USB 2.0
Pulled into next/dt,
* Tero Kristo [181004 14:47]:
> On 04/10/18 17:25, Tony Lindgren wrote:
> > It seems we should just provide a generic interface for
> > clk_allow_autoidle() and clk_deny_autoidle()? Otherwise we'll
> > be forever stuck with pdata callbacks it seems.
>
> The TI clock driver is actually providing
* Tero Kristo [181004 14:47]:
> On 04/10/18 17:25, Tony Lindgren wrote:
> > It seems we should just provide a generic interface for
> > clk_allow_autoidle() and clk_deny_autoidle()? Otherwise we'll
> > be forever stuck with pdata callbacks it seems.
>
> The TI clock driver is actually providing
On Wed, Oct 3, 2018 at 3:45 PM Ludovic Desroches
wrote:
>
> Arnd, Olof,
>
> Here are the second round of DT changes for 4.20. It consists in NAND
> description fixes (size and partitions).
Pulled into next/dt, thanks!
Arnd
On Wed, Oct 3, 2018 at 3:45 PM Ludovic Desroches
wrote:
>
> Arnd, Olof,
>
> Here are the second round of DT changes for 4.20. It consists in NAND
> description fixes (size and partitions).
Pulled into next/dt, thanks!
Arnd
Amir Goldstein wrote:
> @@ -47,7 +47,7 @@ static struct dentry *coda_lookup(struct inode *dir, struct
> dentry *entry, unsig
> int type = 0;
>
> if (length > CODA_MAXNAMLEN) {
> - pr_err("name too long: lookup, %s (%*s)\n",
> + pr_err("name too long:
Amir Goldstein wrote:
> @@ -47,7 +47,7 @@ static struct dentry *coda_lookup(struct inode *dir, struct
> dentry *entry, unsig
> int type = 0;
>
> if (length > CODA_MAXNAMLEN) {
> - pr_err("name too long: lookup, %s (%*s)\n",
> + pr_err("name too long:
On 4 October 2018 at 15:48, Tony Lindgren wrote:
> Hi,
>
> * Ulf Hansson [181003 14:43]:
>> + * GENPD_FLAG_IRQ_SAFE: This informs genpd that its backend
>> callbacks,
>> + * ->power_on|off(), doesn't sleep. Hence, these
>> + * can
On 4 October 2018 at 15:48, Tony Lindgren wrote:
> Hi,
>
> * Ulf Hansson [181003 14:43]:
>> + * GENPD_FLAG_IRQ_SAFE: This informs genpd that its backend
>> callbacks,
>> + * ->power_on|off(), doesn't sleep. Hence, these
>> + * can
On Tue, Oct 02, 2018 at 11:45:07PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> It is not necessary to update data->last_state_idx in menu_select()
> as it only is used in menu_update() which only runs when
> data->needs_update is set and that is set only when updating
>
On Tue, Oct 02, 2018 at 11:45:07PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> It is not necessary to update data->last_state_idx in menu_select()
> as it only is used in menu_update() which only runs when
> data->needs_update is set and that is set only when updating
>
Pavel Snajdr writes:
>
> We started our organization (vpsFree.org) on top of OpenVZ patch set and are
> now
> working to get vanilla up to the task of replacing the venerable 2.6.32-based
> OpenVZ 6 Linux-like thing. The new Code of Conduct is a guarantee for us, that
> we won't be laughed out
Pavel Snajdr writes:
>
> We started our organization (vpsFree.org) on top of OpenVZ patch set and are
> now
> working to get vanilla up to the task of replacing the venerable 2.6.32-based
> OpenVZ 6 Linux-like thing. The new Code of Conduct is a guarantee for us, that
> we won't be laughed out
On Tue, Oct 02, 2018 at 11:44:06PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Rearrange the code in menu_select() so that the loop over idle states
> always starts from 0 and get rid of the first_idx variable.
>
> While at it, add two empty lines to separate conditional
On Tue, Oct 02, 2018 at 11:44:06PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Rearrange the code in menu_select() so that the loop over idle states
> always starts from 0 and get rid of the first_idx variable.
>
> While at it, add two empty lines to separate conditional
A quirk in snd-usb-audio was added to automate setting sample rate to
4800k and remove the previously exposed nonfunctional microphone for
the Bowers & Wilkins PX:
commit 240a8af929c7c57dcde28682725b29cf8474e8e5
https://lore.kernel.org/patchwork/patch/919689/
However the headphones where updated
A quirk in snd-usb-audio was added to automate setting sample rate to
4800k and remove the previously exposed nonfunctional microphone for
the Bowers & Wilkins PX:
commit 240a8af929c7c57dcde28682725b29cf8474e8e5
https://lore.kernel.org/patchwork/patch/919689/
However the headphones where updated
Same for Coda.
uid/gid/mode don't mean anything, access is based on the directory ACL and the
authentication token that is held by the userspace cache manager and ultimately
decided by the servers.
Unless someone broke this recently and made permission checks uid based I would
expect no
Same for Coda.
uid/gid/mode don't mean anything, access is based on the directory ACL and the
authentication token that is held by the userspace cache manager and ultimately
decided by the servers.
Unless someone broke this recently and made permission checks uid based I would
expect no
On 04/10/18 17:25, Tony Lindgren wrote:
* Andreas Kemnade [181004 05:56]:
On the gta04 with a dm3730 omap_hdq does not work properly when the
device enters lower power states. Idling uart1 and 2 is enough
to show up that problem, if there are no other things enabled.
Further research reveals
On 04/10/18 17:25, Tony Lindgren wrote:
* Andreas Kemnade [181004 05:56]:
On the gta04 with a dm3730 omap_hdq does not work properly when the
device enters lower power states. Idling uart1 and 2 is enough
to show up that problem, if there are no other things enabled.
Further research reveals
On 4 October 2018 at 15:59, Alan Cooper wrote:
>> On 4 October 2018 at 11:08, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > If __device_suspend() returns early on an error or pending wakeup
>> > and the power.direct_complete flag has been set for the device
>> > already, the
On 4 October 2018 at 15:59, Alan Cooper wrote:
>> On 4 October 2018 at 11:08, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > If __device_suspend() returns early on an error or pending wakeup
>> > and the power.direct_complete flag has been set for the device
>> > already, the
On 04/10/18 08:51, Andreas Kemnade wrote:
We have the scenario that first autoidle is disabled for all clocks,
then it is disabled for selected ones and then enabled for all. So
we should have some counting here, also according to the
comment in _setup_iclk_autoidle()
Signed-off-by: Andreas
On 04/10/18 08:51, Andreas Kemnade wrote:
We have the scenario that first autoidle is disabled for all clocks,
then it is disabled for selected ones and then enabled for all. So
we should have some counting here, also according to the
comment in _setup_iclk_autoidle()
Signed-off-by: Andreas
On 04.10.2018 16:30, Helge Deller wrote:
> On 04.10.2018 15:34, Arnd Bergmann wrote:
>> On Thu, Oct 4, 2018 at 10:42 AM Helge Deller wrote:
>>> On 04.10.2018 01:02, gregkh wrote:
On Wed, Oct 03, 2018 at 09:49:08PM +0200, Arnd Bergmann wrote:
> On Wed, Oct 3, 2018 at 8:16 PM Greg
On 04.10.2018 16:30, Helge Deller wrote:
> On 04.10.2018 15:34, Arnd Bergmann wrote:
>> On Thu, Oct 4, 2018 at 10:42 AM Helge Deller wrote:
>>> On 04.10.2018 01:02, gregkh wrote:
On Wed, Oct 03, 2018 at 09:49:08PM +0200, Arnd Bergmann wrote:
> On Wed, Oct 3, 2018 at 8:16 PM Greg
Hi Boris
On Thu, Oct 4, 2018 at 4:02 PM Boris Brezillon
wrote:
>
> On Thu, 4 Oct 2018 15:01:09 +0200
> Ricardo Ribalda Delgado wrote:
>
> > Add documentation for gpio-addr-flash. This binding allow creating
> > flash devices that are paged using GPIOs.
> >
> > Cc: devicet...@vger.kernel.org
> >
Hi Boris
On Thu, Oct 4, 2018 at 4:02 PM Boris Brezillon
wrote:
>
> On Thu, 4 Oct 2018 15:01:09 +0200
> Ricardo Ribalda Delgado wrote:
>
> > Add documentation for gpio-addr-flash. This binding allow creating
> > flash devices that are paged using GPIOs.
> >
> > Cc: devicet...@vger.kernel.org
> >
On 04.10.2018 15:34, Arnd Bergmann wrote:
> On Thu, Oct 4, 2018 at 10:42 AM Helge Deller wrote:
>> On 04.10.2018 01:02, gregkh wrote:
>>> On Wed, Oct 03, 2018 at 09:49:08PM +0200, Arnd Bergmann wrote:
On Wed, Oct 3, 2018 at 8:16 PM Greg Kroah-Hartman
wrote:
> On Wed, Oct 03, 2018
* Aaro Koskinen [181002 17:52]:
> Hi,
>
> On Tue, Oct 02, 2018 at 11:45:29AM +0200, Janusz Krzysztofik wrote:
> > Since the very beginning, unsigned int .irq member of struct
> > plat_serial8250_port introduced by commit eff443df679e ("OMAP1:
> > AMS_DELTA: add modem support") was statically
On 04.10.2018 15:34, Arnd Bergmann wrote:
> On Thu, Oct 4, 2018 at 10:42 AM Helge Deller wrote:
>> On 04.10.2018 01:02, gregkh wrote:
>>> On Wed, Oct 03, 2018 at 09:49:08PM +0200, Arnd Bergmann wrote:
On Wed, Oct 3, 2018 at 8:16 PM Greg Kroah-Hartman
wrote:
> On Wed, Oct 03, 2018
* Aaro Koskinen [181002 17:52]:
> Hi,
>
> On Tue, Oct 02, 2018 at 11:45:29AM +0200, Janusz Krzysztofik wrote:
> > Since the very beginning, unsigned int .irq member of struct
> > plat_serial8250_port introduced by commit eff443df679e ("OMAP1:
> > AMS_DELTA: add modem support") was statically
Allow creating gpio-addr-flash via device-tree and not just via platform
data.
Mimic what physmap_of_versatile and physmap_of_gemini does to reduce
code duplicity.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/Kconfig | 8 +++
drivers/mtd/maps/Makefile | 3 +-
Allow creating gpio-addr-flash via device-tree and not just via platform
data.
Mimic what physmap_of_versatile and physmap_of_gemini does to reduce
code duplicity.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/Kconfig | 8 +++
drivers/mtd/maps/Makefile | 3 +-
Add documentation for gpio-addr-flash. This binding allow creating
flash devices that are paged using GPIOs.
Cc: devicet...@vger.kernel.org
Reviewed-by: Rob Herring
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 2 ++
1 file changed, 2
Add documentation for gpio-addr-flash. This binding allow creating
flash devices that are paged using GPIOs.
Cc: devicet...@vger.kernel.org
Reviewed-by: Rob Herring
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 2 ++
1 file changed, 2
On 10/3/18 8:37 PM, Nathan Chancellor wrote:
> Clang warns when one enumerated type is implicitly converted to another.
>
> drivers/ata/pata_ep93xx.c:662:36: warning: implicit conversion from
> enumeration type 'enum dma_data_direction' to different enumeration type
> 'enum
On 10/3/18 8:37 PM, Nathan Chancellor wrote:
> Clang warns when one enumerated type is implicitly converted to another.
>
> drivers/ata/pata_ep93xx.c:662:36: warning: implicit conversion from
> enumeration type 'enum dma_data_direction' to different enumeration type
> 'enum
* Andreas Kemnade [181004 05:56]:
> On the gta04 with a dm3730 omap_hdq does not work properly when the
> device enters lower power states. Idling uart1 and 2 is enough
> to show up that problem, if there are no other things enabled.
> Further research reveals that hdq iclk must not be turned off
* Andreas Kemnade [181004 05:56]:
> On the gta04 with a dm3730 omap_hdq does not work properly when the
> device enters lower power states. Idling uart1 and 2 is enough
> to show up that problem, if there are no other things enabled.
> Further research reveals that hdq iclk must not be turned off
On Thu, Sep 06, 2018 at 02:45:04AM -0700, Palmer Dabbelt wrote:
> On Sun, 26 Aug 2018 18:07:50 PDT (-0700), alan...@andestech.com wrote:
> >This patchset adds an option, CONFIG_FPU, to enable/disable floating-
> >point procedures.
> >
> >Kernel's new behavior will be as follows:
> >
> >* with
On Thu, Sep 06, 2018 at 02:45:04AM -0700, Palmer Dabbelt wrote:
> On Sun, 26 Aug 2018 18:07:50 PDT (-0700), alan...@andestech.com wrote:
> >This patchset adds an option, CONFIG_FPU, to enable/disable floating-
> >point procedures.
> >
> >Kernel's new behavior will be as follows:
> >
> >* with
On Tue, Oct 02, 2018 at 11:42:56PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Since menu_select() can only set first_idx to 1 if the exit latency
> of the second state is not greater than the latency limit, it should
> first determine that limit. Thus first_idx should be
On Tue, Oct 02, 2018 at 11:42:56PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Since menu_select() can only set first_idx to 1 if the exit latency
> of the second state is not greater than the latency limit, it should
> first determine that limit. Thus first_idx should be
On Thu, 04 Oct 2018 16:11:42 +0200
Janusz Krzysztofik wrote:
>
> Legacy nand_wait_ready() uses a hardcoded timeout value of 400 ms. Should
> we
> follow the same approach in nand_gpio_waitrdy(), or should we rather let
> drivers pass the timeout value, like in case of nand_soft_waitrdy()?
On Thu, 04 Oct 2018 16:11:42 +0200
Janusz Krzysztofik wrote:
>
> Legacy nand_wait_ready() uses a hardcoded timeout value of 400 ms. Should
> we
> follow the same approach in nand_gpio_waitrdy(), or should we rather let
> drivers pass the timeout value, like in case of nand_soft_waitrdy()?
On Thu, Oct 4, 2018 at 3:47 PM Guenter Roeck wrote:
> Time for a status report.
>
> Build results:
> total: 135 pass: 121 fail: 14
> Failed builds:
> arm:allmodconfig
> i386:allyesconfig
> i386:allmodconfig
> m68k:defconfig
> m68k:allmodconfig
>
On Thu, Oct 4, 2018 at 3:47 PM Guenter Roeck wrote:
> Time for a status report.
>
> Build results:
> total: 135 pass: 121 fail: 14
> Failed builds:
> arm:allmodconfig
> i386:allyesconfig
> i386:allmodconfig
> m68k:defconfig
> m68k:allmodconfig
>
Dear RT Folks,
This is the RT stable review cycle of patch v4.4.148-rt166-rc1.
Please scream at me if I messed something up. Please test the patches
too.
The -rc release will be uploaded to kernel.org and will be deleted
when the final release is out. This is just a review release (or
release
Dear RT Folks,
This is the RT stable review cycle of patch v4.4.148-rt166-rc1.
Please scream at me if I messed something up. Please test the patches
too.
The -rc release will be uploaded to kernel.org and will be deleted
when the final release is out. This is just a review release (or
release
NeilBrown wrote:
> diff --git a/fs/afs/security.c b/fs/afs/security.c
> index 81dfedb7879f..ac2e39de8bff 100644
> --- a/fs/afs/security.c
> +++ b/fs/afs/security.c
> @@ -349,6 +349,16 @@ int afs_permission(struct inode *inode, int mask)
> if (mask & MAY_NOT_BLOCK)
> return
NeilBrown wrote:
> diff --git a/fs/afs/security.c b/fs/afs/security.c
> index 81dfedb7879f..ac2e39de8bff 100644
> --- a/fs/afs/security.c
> +++ b/fs/afs/security.c
> @@ -349,6 +349,16 @@ int afs_permission(struct inode *inode, int mask)
> if (mask & MAY_NOT_BLOCK)
> return
On Thu, Oct 4, 2018 at 3:48 PM Michael Schupikov wrote:
>
> Remove one include of .
> No functional changes.
>
> Signed-off-by: Michael Schupikov
> ---
> kernel/sysctl.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index cc02050fd0c4..523cb36b72eb
On Thu, Oct 4, 2018 at 3:48 PM Michael Schupikov wrote:
>
> Remove one include of .
> No functional changes.
>
> Signed-off-by: Michael Schupikov
> ---
> kernel/sysctl.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index cc02050fd0c4..523cb36b72eb
601 - 700 of 1300 matches
Mail list logo
