RE: [PATCH v2] mmc: sdhci-pci: SDIO host controller support for Intel Quark X1000

-Original Message- From: Ulf Hansson [mailto:ulf.hans...@linaro.org] Sent: Wednesday, July 02, 2014 5:01 PM To: Chen, Alvin Cc: Chris Ball; linux-mmc; linux-kernel@vger.kernel.org; Ong, Boon Leong Subject: Re: [PATCH v2] mmc: sdhci-pci: SDIO host controller support for Intel Quark

RE: [PATCH 2/2] x86: Quark: Comment setup_arch for TLB/PGE bugfix

-Original Message- From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- ow...@vger.kernel.org] On Behalf Of Bryan O'Donoghue Sent: Wednesday, October 01, 2014 7:42 AM To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; da...@redhat.com; h...@hmh.eng.br Cc:

[PATCH] x86, setup: Additional __flush_tlb for Quak X1000

for Quark SoC. FYI, the suggestion to add __flush_tlb() has been discussed with some of the kernel developers CC'ed below inclusing HPA himself. Thank you very much, Ong Boon Leong Ong Boon Leong (1): x86, setup: add __flush_tlb() for Intel Quark X1000 arch/x86/kernel/setup.c |7 +++ 1

[PATCH] x86, setup: add __flush_tlb() for Intel Quark X1000

reference to __flush_tlb_all() is mapped to __flush_tlb(). As this is early stage of kernel boot-up and adding __flush_tlb() is not going to hurt much in CPU cycles, we add it here and together with the explanation for future reference. Signed-off-by: Ong Boon Leong boon.leong@intel.com --- arch

RE: [PATCH v2] x86: Quark: Add if/else to setup_arch for Quark TLB bug

My view is that the CR3 load should have flushed the TLB in it's entirety. Ong Boong Leong said that a discussion he had which included HPA concluded with a flush of the TLB being required after the CR3 reload. The proposed patch was discussed in April and after much thought into this, I

RE: [PATCH v8 1/2] x86: Add Isolated Memory Regions for Quark X1000

_text Thanks Bryan. -Original Message- From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] Sent: Saturday, January 31, 2015 12:30 AM To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org; dvh...@infradead.org; andy.shevche...@gmail.com; Ong, Boon Leong; linux

[PATCH] Intel Quark X1000 DTS thermal driver

. Please kindly review the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. Ong Boon Leong (1): thermal: intel Quark SoC X1000 DTS thermal driver drivers/thermal/Kconfig | 10 drivers

[PATCH] thermal: intel Quark SoC X1000 DTS thermal driver

temperature $ cat temp - to read critical trip point $ cat trip_point_0_temp - to read trip point type $ cat trip_point_0_type - to emulate temperature raise to test orderly shutdown by Linux distro $ echo 105 emul_temp Signed-off-by: Ong Boon Leong boon.leong@intel.com --- drivers

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

On 29/01/15 15:40, Bryan O'Donoghue wrote: It would be nice to have two variants (1) index based (2) address based. Understood. The direction from Ingo was to have address based external interface imr_del_range() and support an index based internal imr_clear() - internally. So - in order

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

, wmask=0x0001, enabled , locked -Original Message- From: Ong, Boon Leong Sent: Thursday, January 29, 2015 9:47 PM To: 'Bryan O'Donoghue' Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x...@kernel.org; dvh...@infradead.org; linux-kernel@vger.kernel.org; Andy Shevchenko; Ingo Molnar

RE: [PATCH] x86: Re-enable IO-APIC for non-SMP X86_32

-by: Ong Boon Leong boon.leong@intel.com --- arch/x86/Kconfig | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index ba397bd..0dc9d01 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -857,7 +857,7 @@ source kernel/Kconfig.preempt

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

Bryan, a minor fix on the config below... diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug index 61bd2ad..fcf5701 100644 --- a/arch/x86/Kconfig.debug +++ b/arch/x86/Kconfig.debug @@ -313,6 +313,18 @@ config DEBUG_NMI_SELFTEST If unsure, say N. +config DEBUG_IMR_SELFTEST +

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

-Original Message- From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] Sent: Thursday, January 29, 2015 11:22 PM To: Ong, Boon Leong Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x...@kernel.org; dvh...@infradead.org; linux-kernel@vger.kernel.org; Andy Shevchenko; Ingo

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x...@kernel.org; dvh...@infradead.org; Ong, Boon Leong; linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000 On 29/01/15 10:08, Andy Shevchenko wrote: On Thu, Jan 29, 2015 at 9:44 AM, Ingo Molnar mi

RE: [PATCH v2 1/1] x86: Add Isolated Memory Regions for Quark X1000

...@infradead.org; andy.shevche...@gmail.com; Ong, Boon Leong; linux- ker...@vger.kernel.org Cc: Bryan O'Donoghue Subject: [PATCH v2 1/1] x86: Add Isolated Memory Regions for Quark X1000 From V1 comment: Suggest to add a statement on 3 different types of IMR: General IMR, Host Memory I/O Boundary IMR

RE: [PATCH 2/2] platform/x86: Add Intel Galileo platform specific setup

Subject: [PATCH 2/2] platform/x86: Add Intel Galileo platform specific setup [snippet removed] Since the Quark EFI bringup code configures the system to reset on an IMR Typo: bring-up violation, this means that common operations such as mouting an SD based root Typo: mounting [snippet removed]

[PATCH] mfd, lpc_sch: Intel Quark X1000 WDT enabling

=val in second To activate warm reset enable reset, we use kernel param:- ie6xx_wdt.resetmode=0x18 Thank you very much Ong Boon Leong Intel Corp. Ong Boon Leong (1): mfd: lpc_sch: enable WDT for Intel Quark X1000 drivers/mfd/lpc_sch.c |1 1 file changed, 1

[PATCH] mfd: lpc_sch: enable WDT for Intel Quark X1000

Quark X1000 uses ie6xx_wdt driver for WDT. To enable WDT, we declare WDT IO resource size for Quark X1000. Signed-off-by: Ong Boon Leong boon.leong@intel.com --- drivers/mfd/lpc_sch.c |1 1 file changed, 1 insertion(+) diff --git a/drivers/mfd/lpc_sch.c b/drivers/mfd/lpc_sch.c index

RE: [PATCH 2/2] platform/x86: Add Intel Galileo platform specific setup

On 09/01/15 11:17, Bryan O'Donoghue wrote: So this will load on any Quark device, Galileo or not, that doesn't provide a system_id. Is there any reason we need to support 0.8.0 and earlier firmware? Every Galileo Gen1 device ships with firmware version 0.7.5. You can do an EFI capsule

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

On 07/01/15 23:45, Ong, Boon Leong wrote: Since BIOS and grub code both use 0x as the 'off' address I think it makes sense for the kernel to continue to use that address. Just add on top of what Daren mentioned in another mail, based on the Quark document, the base address can start

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

+/** + * imr_del_range - Delete an Isolated Memory Region + * @reg: IMR index to remove + * @base: Physical base address of region aligned to 4k + * @size: Physical size of region in bytes + * @return:-EINVAL on invalid range or out or range id + * -ENODEV if reg is valid

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

+/** + * imr_enabled + * Determines if an IMR is enabled based on address range + * + * @imr: Pointer to IMR descriptor + * @return true if IMR enabled false if disabled + */ +static int imr_enabled(struct imr *imr) { + return (imr_to_phys(imr-addr_lo) imr_to_phys(imr-addr_hi));

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

-Original Message- From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- ow...@vger.kernel.org] On Behalf Of Bryan O'Donoghue Sent: Monday, December 29, 2014 9:23 AM To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org; dvh...@infradead.org;

[PATCHv3 0/1] Intel Quark X1000 DTS thermal driver

the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v3: * Kconfig dependency changed to X86_INTEL_QUARK Changes in v2: * Fix several commit write-up grammar, choice of words. * Ensure int ret

[PATCHv3 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

Signed-off-by: Ong Boon Leong boon.leong@intel.com Reviewed-by: Bryan O'Donoghue pure.lo...@nexus-software.ie --- drivers/thermal/Kconfig | 10 + drivers/thermal/Makefile |1 + drivers/thermal/intel_quark_dts_thermal.c | 434 + 3

RE: [PATCHv3 0/1] Intel Quark X1000 DTS thermal driver

Dear maintainer, gentle ping if this driver is ready for more review/inclusion into Linux v4.1 ? Thank you very much. -Original Message- From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- ow...@vger.kernel.org] On Behalf Of Ong Boon Leong Sent: Monday, March 9, 2015 3:43 PM

RE: [PATCH] x86/quark: Run IMR self-test on IMR capble hw only

; Shevchenko, Andriy; Ong, Boon Leong; dvh...@linux.intel.com; linux- ker...@vger.kernel.org Subject: [PATCH] x86/quark: Run IMR self-test on IMR capble hw only Automated testing with LKP shows IMR self test code running and printing error messages on QEMU hardware lacking IMR support. Update IMR

RE: [PATCH v2 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

-Original Message- From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] Sent: Tuesday, March 3, 2015 12:12 AM To: Ong, Boon Leong; Zhang, Rui; edubez...@gmail.com; Kweh, Hock Leong Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/1] thermal: intel

RE: [PATCH v2 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

-Original Message- From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] Sent: Friday, March 6, 2015 12:11 AM To: Ong, Boon Leong Cc: Bryan O'Donoghue; Zhang, Rui; edubez...@gmail.com; Kweh, Hock Leong; linux...@vger.kernel.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/1

RE: [PATCH v1 1/1] x86/intel/quark: select COMMON_CLK

Yup, this is right. Thanks Andy. -Original Message- From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] Sent: Thursday, March 5, 2015 11:24 PM To: Ong, Boon Leong; Ingo Molnar; Darren Hart; Bryan O'Donoghue; x...@kernel.org; linux-kernel@vger.kernel.org Cc: Andy Shevchenko

[PATCH v2 0/1] Intel Quark X1000 DTS thermal driver

. Please kindly review the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v2: * Fix several commit write-up grammar, choice of words. * Ensure int ret in correct order * Add comment

[PATCH v2 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

temperature $ cat temp - to read critical trip point $ cat trip_point_0_temp - to read trip point type $ cat trip_point_0_type - to emulate temperature raise to test orderly shutdown by Linux distro $ echo 105 emul_temp Signed-off-by: Ong Boon Leong boon.leong@intel.com

RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver

-Original Message- From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- ow...@vger.kernel.org] On Behalf Of Ong, Boon Leong Sent: Monday, February 23, 2015 9:39 AM To: Kweh, Hock Leong; Zhang, Rui; edubez...@gmail.com Cc: linux...@vger.kernel.org; LKML; Bryan O'Donoghue Subject

RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver

-Original Message- From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] Sent: Thursday, February 12, 2015 7:37 PM To: Ong, Boon Leong; Zhang, Rui; edubez...@gmail.com Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH] thermal: intel Quark SoC X1000 DTS

RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver

Just to bring out for discussion, do you think we should put a safety range for reporting out the critical trip temperature value (mean the value from register minus 1 or 2 degree)? Just wondering if this is needed for the software to have the sufficient shutdown time before the HW make a hard

RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver

-Original Message- From: Kweh, Hock Leong Sent: Monday, February 23, 2015 3:39 PM To: Ong, Boon Leong; Zhang, Rui; edubez...@gmail.com Cc: linux...@vger.kernel.org; LKML; Bryan O'Donoghue Subject: RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver -Original Message

RE: [PATCH v7 2/2] x86, quark: Add Intel Quark platform support

...@gmail.com; Ong, Boon Leong; linux- ker...@vger.kernel.org Cc: Bryan O'Donoghue Subject: [PATCH v7 2/2] x86, quark: Add Intel Quark platform support Add Intel Quark platform support. Quark needs to pull down all unlocked IMRs to ensure agreement with the EFI memory map post boot. This patch adds

RE: [PATCH v7 1/2] x86: Add Isolated Memory Regions for Quark X1000

...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org; dvh...@infradead.org; andy.shevche...@gmail.com; Ong, Boon Leong; linux- ker...@vger.kernel.org Cc: Bryan O'Donoghue Subject: [PATCH v7 1/2] x86: Add Isolated Memory Regions for Quark X1000 Intel's Quark X1000 SoC contains a set

[PATCHv5 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

Signed-off-by: Ong Boon Leong boon.leong@intel.com Reviewed-by: Bryan O'Donoghue pure.lo...@nexus-software.ie Reviewed-by: Kweh, Hock Leong hock.leong.k...@intel.com --- drivers/thermal/Kconfig | 10 + drivers/thermal/Makefile |1 + drivers/thermal

[PATCHv5 0/1] Intel Quark X1000 DTS thermal driver

the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v5: * Added BSD License as reported by Paul Bolle pebo...@tiscali.nl. Changes in v4: * Fixed unused variable 'aux_entry' as reported

[PATCHv6 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

Signed-off-by: Ong Boon Leong boon.leong@intel.com Reviewed-by: Bryan O'Donoghue pure.lo...@nexus-software.ie Reviewed-by: Kweh, Hock Leong hock.leong.k...@intel.com --- drivers/thermal/Kconfig | 10 + drivers/thermal/Makefile |1 + drivers/thermal

[PATCHv6 0/1] Intel Quark X1000 DTS thermal driver

the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v6: * Revised to use the recommended dual license style per feedback from Rui. Thanks! Changes in v5: * Added BSD License as reported

RE: [PATCH v5 2/2] efi: a misc char interface for user to update efi firmware

>OK, that's interesting. Which cat tool is included with the Quark BSP? > Quark is using busybox 1.22.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

RE: [PATCH v2 1/1] x86/platform/iosf_mbi: Remove duplicate definitions

>-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Andy Shevchenko >Sent: Wednesday, November 25, 2015 10:33 PM >To: Thomas Gleixner >Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;

RE: [PATCH v2] mmc: sdhci-pci: SDIO host controller support for Intel Quark X1000

> -Original Message- > From: Ulf Hansson [mailto:ulf.hans...@linaro.org] > Sent: Wednesday, July 02, 2014 5:01 PM > To: Chen, Alvin > Cc: Chris Ball; linux-mmc; linux-kernel@vger.kernel.org; Ong, Boon Leong > Subject: Re: [PATCH v2] mmc: sdhci-pci: SDIO host controller

RE: [PATCH v1 net-next] net: phy: mdio_bus: make mdiobus_scan also cover PHY that only talks C45

>On Tue, Aug 27, 2019 at 03:23:34PM +, Voon, Weifeng wrote: >> > > > Make mdiobus_scan() to try harder to look for any PHY that only >> > talks C45. >> > > If you are not using Device Tree or ACPI, and you are letting the MDIO >> > > bus be scanned, it sounds like there should be a way for you

[RFC net-next v1 0/5] PHY converter driver for DW xPCS IP

e PHY converter driver and mdio device through DT definition. Please kindly review this RFC and provide any feedback/concern that the community may have. Appreciate your time here. Thanks Boon Leong Ong Boon Leong (5): net: phy: make mdiobus_create_device() function callable from Eth dr

[RFC net-next v1 1/5] net: phy: make mdiobus_create_device() function callable from Eth driver

make mdiobus_create_ device() to be callable from Eth driver open(). Signed-off-by: Ong Boon Leong --- drivers/net/phy/mdio_bus.c | 5 +++-- include/linux/phy.h| 7 +++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy

[RFC net-next v1 2/5] net: phy: introduce mdiobus_get_mdio_device

Add the function to get mdio_device based on the mdio addr. Signed-off-by: Ong Boon Leong --- drivers/net/phy/mdio_bus.c | 6 ++ include/linux/mdio.h | 1 + 2 files changed, 7 insertions(+) diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c index 06658d9197a1

[RFC net-next v1 4/5] net: phy: introducing support for DWC xPCS logics for EHL & TGL

Hock Leong Signed-off-by: Ong Boon Leong --- drivers/net/phy/Kconfig | 9 + drivers/net/phy/Makefile | 1 + drivers/net/phy/dwxpcs.c | 417 +++ include/linux/dwxpcs.h | 16 ++ 4 files changed, 443 insertions(+) create mode 100644 drivers/net/phy/dwxpcs

[RFC net-next v1 3/5] net: phy: add private data to mdio_device

PHY converter device is represented as mdio_device and requires private data. So, we add pointer for private data to mdio_device struct. Signed-off-by: Ong Boon Leong --- include/linux/mdio.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/mdio.h b/include/linux/mdio.h index

[RFC net-next v1 5/5] net: stmmac: add dwxpcs boardinfo for mdio_device registration

GMII interface only. Also introduce callback for remove mdio_device for unloading driver. Signed-off-by: Ong Boon Leong --- drivers/net/ethernet/stmicro/stmmac/Kconfig | 1 + drivers/net/ethernet/stmicro/stmmac/stmmac.h | 2 + .../net/ethernet/stmicro/stmmac/stmmac_main.c | 25 +++ ...

[RFC net-next v2 1/5] net: phy: make mdiobus_create_device() function callable from Eth driver

make mdiobus_create_ device() to be callable from Eth driver open(). Signed-off-by: Ong Boon Leong --- drivers/net/phy/mdio_bus.c | 5 +++-- include/linux/phy.h| 7 +++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy

[RFC net-next v2 2/5] net: phy: introduce mdiobus_get_mdio_device

Add the function to get mdio_device based on the mdio addr. Signed-off-by: Ong Boon Leong --- drivers/net/phy/mdio_bus.c | 6 ++ include/linux/mdio.h | 1 + 2 files changed, 7 insertions(+) diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c index 06658d9197a1

[RFC net-next v2 0/5] PHY converter driver for DW xPCS IP

e here. Thanks Boon Leong Ong Boon Leong (5): net: phy: make mdiobus_create_device() function callable from Eth driver net: phy: introduce mdiobus_get_mdio_device net: phy: add private data to mdio_device net: phy: introducing support for DWC xPCS logics for EHL & TGL net: stmmac: a

[RFC net-next v2 4/5] net: phy: introducing support for DWC xPCS logics for EHL & TGL

Hock Leong Signed-off-by: Ong Boon Leong --- drivers/net/phy/Kconfig | 9 + drivers/net/phy/Makefile | 1 + drivers/net/phy/dwxpcs.c | 417 +++ include/linux/dwxpcs.h | 16 ++ 4 files changed, 443 insertions(+) create mode 100644 drivers/net/phy/dwxpcs

[RFC net-next v2 3/5] net: phy: add private data to mdio_device

PHY converter device is represented as mdio_device and requires private data. So, we add pointer for private data to mdio_device struct. Signed-off-by: Ong Boon Leong --- include/linux/mdio.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/mdio.h b/include/linux/mdio.h index

[RFC net-next v2 5/5] net: stmmac: add dwxpcs boardinfo for mdio_device registration

GMII interface only. Also introduce callback for remove mdio_device for unloading driver. Signed-off-by: Ong Boon Leong --- drivers/net/ethernet/stmicro/stmmac/Kconfig | 1 + drivers/net/ethernet/stmicro/stmmac/stmmac.h | 2 + .../net/ethernet/stmicro/stmmac/stmmac_main.c | 25 +++ ...

RE: [RFC net-next 1/5] net: stmmac: introduce IEEE 802.1Qbv configuration functionalities

>-Original Message- >From: Jose Abreu [mailto:jose.ab...@synopsys.com] >>From: Voon Weifeng >> diff --git a/drivers/net/ethernet/stmicro/stmmac/dw_tsn_lib.c >b/drivers/net/ethernet/stmicro/stmmac/dw_tsn_lib.c >> new file mode 100644 >> index ..cba27c604cb1 >> --- /dev/null >>

RE: [PATCH net-next v6 2/5] net: stmmac: introducing support for DWC xPCS logics

eppe >Cavallaro ; Andrew Lunn ; >Alexandre Torgue ; biao huang >; Ong, Boon Leong >; Kweh, Hock Leong > >Subject: RE: [PATCH net-next v6 2/5] net: stmmac: introducing support for >DWC xPCS logics > >From: Florian Fainelli > >> +Russell, >> >

RE: [RFC net-next 1/5] net: stmmac: introduce IEEE 802.1Qbv configuration functionalities

>> > It looks like most o the TSN_WARN should actually be netdev_dbg(). >> > >> >Andrew >> >> Hi Andrew, >> This file is targeted for dual licensing which is GPL-2.0 OR BSD-3-Clause. >> This is the reason why we are using wrappers around the functions so that >> all the function call is

RE: [RFC net-next 1/5] net: stmmac: introduce IEEE 802.1Qbv configuration functionalities

>-Original Message- >From: Gomes, Vinicius >> +++ b/drivers/net/ethernet/stmicro/stmmac/dw_tsn_lib.c >> @@ -0,0 +1,790 @@ >> + >> +static struct tsn_hw_cap dw_tsn_hwcap; >> +static bool dw_tsn_feat_en[TSN_FEAT_ID_MAX]; >> +static unsigned int dw_tsn_hwtunable[TSN_HWTUNA_MAX]; >> +static

RE: [PATCH net-next v6 2/5] net: stmmac: introducing support for DWC xPCS logics

>>From: Jose Abreu [mailto:jose.ab...@synopsys.com] >>From: Florian Fainelli >> >>> +Russell, >>> >>> On 6/4/2019 11:58 AM, Voon Weifeng wrote: >>> > From: Ong Boon Leong >>> > >>> > xPCS is DWC Ethernet Physical

RE: [PATCH 4/7] net: stmmac: introducing support for DWC xPCS logics

>-Original Message- >From: Andrew Lunn [mailto:and...@lunn.ch] >Sent: Thursday, April 25, 2019 11:21 AM >To: Ong, Boon Leong >Cc: David S. Miller ; net...@vger.kernel.org; linux- >ker...@vger.kernel.org; Kweh, Hock Leong ; >Voon, Weifeng >Subject: Re: [PATCH 4/7]

RE: [PATCH 2/2] net-next: stmmac: add mdio clause 45 access from mac device for dwmac4

>Subject: [PATCH 2/2] net-next: stmmac: add mdio clause 45 access from mac >device for dwmac4 > >add clause 45 mdio read and write from mac device for dwmac4. > >Signed-off-by: Biao Huang Hi, I would like to point out that there is another C45 implementation proposed here "net: stmmac: enable

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

>>> +/** >>> + * imr_enabled >>> + * Determines if an IMR is enabled based on address range >>> + * >>> + * @imr: Pointer to IMR descriptor >>> + * @return true if IMR enabled false if disabled >>> + */ >>> +static int imr_enabled(struct imr *imr) { >>> + return (imr_to_phys(imr->addr_lo) &&

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

>-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Bryan O'Donoghue >Sent: Monday, December 29, 2014 9:23 AM >To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org; >dvh...@infradead.org;

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

>>> +/** >>> + * imr_del_range - Delete an Isolated Memory Region >>> + * @reg: IMR index to remove >>> + * @base: Physical base address of region aligned to 4k >>> + * @size: Physical size of region in bytes >>> + * @return:-EINVAL on invalid range or out or range id >>> + *

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

>On 07/01/15 23:45, Ong, Boon Leong wrote: >>> Since BIOS and grub code both use 0x as the 'off' address I >>> think it makes sense for the kernel to continue to use that address. >> >> Just add on top of what Daren mentioned in another mail, based o

RE: [PATCH v2] x86: Quark: Add if/else to setup_arch for Quark TLB bug

> > My view is that the CR3 load should have flushed the TLB in it's entirety. > > Ong Boong Leong said that a discussion he had which included HPA concluded > with a flush of the TLB being required after the CR3 reload. The proposed patch was discussed in April and after much thought into

[PATCH] x86, setup: Additional __flush_tlb for Quak X1000

Bryan for submitting patch for Quark SoC. FYI, the suggestion to add __flush_tlb() has been discussed with some of the kernel developers CC'ed below inclusing HPA himself. Thank you very much, Ong Boon Leong Ong Boon Leong (1): x86, setup: add __flush_tlb() for Intel Quark X1000 arch

[PATCH] x86, setup: add __flush_tlb() for Intel Quark X1000

future reference to __flush_tlb_all() is mapped to __flush_tlb(). As this is early stage of kernel boot-up and adding __flush_tlb() is not going to hurt much in CPU cycles, we add it here and together with the explanation for future reference. Signed-off-by: Ong Boon Leong --- arch/x86/kernel/s

RE: [PATCHv3 0/1] Intel Quark X1000 DTS thermal driver

Dear maintainer, gentle ping if this driver is ready for more review/inclusion into Linux v4.1 ? Thank you very much. >-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Ong Boon Leong >Sent: Monday, March

RE: [PATCH] x86/quark: Run IMR self-test on IMR capble hw only

huang.ying.cari...@gmail.com; >Shevchenko, Andriy; Ong, Boon Leong; dvh...@linux.intel.com; linux- >ker...@vger.kernel.org >Subject: [PATCH] x86/quark: Run IMR self-test on IMR capble hw only > >Automated testing with LKP shows IMR self test code running and printing >error messages on

RE: [PATCH v2 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

>-Original Message- >From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] >Sent: Tuesday, March 3, 2015 12:12 AM >To: Ong, Boon Leong; Zhang, Rui; edubez...@gmail.com; Kweh, Hock Leong >Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org >Subject: Re: [PAT

RE: [PATCH v5 2/2] efi: a misc char interface for user to update efi firmware

>OK, that's interesting. Which cat tool is included with the Quark BSP? > Quark is using busybox 1.22.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH] mfd, lpc_sch: Intel Quark X1000 WDT enabling

= To activate warm reset & enable reset, we use kernel param:- ie6xx_wdt.resetmode=0x18 Thank you very much Ong Boon Leong Intel Corp. Ong Boon Leong (1): mfd: lpc_sch: enable WDT for Intel Quark X1000 drivers/mfd/lpc_sch.c |1 1 file changed, 1 inser

[PATCH] mfd: lpc_sch: enable WDT for Intel Quark X1000

Quark X1000 uses ie6xx_wdt driver for WDT. To enable WDT, we declare WDT IO resource size for Quark X1000. Signed-off-by: Ong Boon Leong --- drivers/mfd/lpc_sch.c |1 1 file changed, 1 insertion(+) diff --git a/drivers/mfd/lpc_sch.c b/drivers/mfd/lpc_sch.c index 5c38df3..a56e4ba 100644

RE: [PATCH 2/2] platform/x86: Add Intel Galileo platform specific setup

>Subject: [PATCH 2/2] platform/x86: Add Intel Galileo platform specific setup > [snippet removed] >Since the Quark EFI bringup code configures the system to reset on an IMR Typo: bring-up >violation, this means that common operations such as mouting an SD based root Typo: mounting [snippet

RE: [PATCH 2/2] platform/x86: Add Intel Galileo platform specific setup

> >On 09/01/15 11:17, Bryan O'Donoghue wrote: >>> So this will load on any Quark device, Galileo or not, that doesn't >>> provide a system_id. Is there any reason we need to support 0.8.0 and >>> earlier firmware? >> >> Every Galileo Gen1 device ships with firmware version 0.7.5. You can >> do an

RE: [PATCH v2 1/1] x86: Add Isolated Memory Regions for Quark X1000

x...@kernel.org; >dvh...@infradead.org; andy.shevche...@gmail.com; Ong, Boon Leong; linux- >ker...@vger.kernel.org >Cc: Bryan O'Donoghue >Subject: [PATCH v2 1/1] x86: Add Isolated Memory Regions for Quark X1000 > >From V1 comment: Suggest to add a statement on 3 different types of

RE: [PATCH v8 1/2] x86: Add Isolated Memory Regions for Quark X1000

_text Thanks Bryan. >-Original Message- >From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] >Sent: Saturday, January 31, 2015 12:30 AM >To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org; >dvh...@infradead.org; andy.shevche...@gmail.com;

RE: [PATCH 2/2] x86: Quark: Comment setup_arch for TLB/PGE bugfix

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Bryan O'Donoghue > Sent: Wednesday, October 01, 2014 7:42 AM > To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; > da...@redhat.com; h...@hmh.eng.br > Cc:

[PATCHv5 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

_ids) || !iosf_mbi_available()) + return -ENODEV; + + soc_dts = alloc_soc_dts(); + if (IS_ERR(soc_dts)) { + err = PTR_ERR(soc_dts); + goto err_free; + } + + return 0; + +err_free: + free_soc_dts(soc_dts); + return

[PATCHv5 0/1] Intel Quark X1000 DTS thermal driver

dly review the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v5: * Added BSD License as reported by Paul Bolle . Changes in v4: * Fixed unused variable 'aux_entry' as reported by kbuild-

[PATCHv6 0/1] Intel Quark X1000 DTS thermal driver

dly review the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v6: * Revised to use the recommended dual license style per feedback from Rui. Thanks! Changes in v5: * Added BSD License a

[PATCHv6 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

hope that it will be useful, but + * WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * General Public License for more details. + * + * Contact Information: + * Ong Boon Leong + * Intel Malaysia, Penang + *

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

Bryan, a minor fix on the config below... >diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug index >61bd2ad..fcf5701 100644 >--- a/arch/x86/Kconfig.debug >+++ b/arch/x86/Kconfig.debug >@@ -313,6 +313,18 @@ config DEBUG_NMI_SELFTEST > > If unsure, say N. > >+config

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

nko; Ingo Molnar >Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x...@kernel.org; >dvh...@infradead.org; Ong, Boon Leong; linux-kernel@vger.kernel.org >Subject: Re: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000 > >On 29/01/15 10:08, Andy Shevchenko wrote: >>

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

0x0001, wmask=0x0001, enabled , locked >-Original Message----- >From: Ong, Boon Leong >Sent: Thursday, January 29, 2015 9:47 PM >To: 'Bryan O'Donoghue' >Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x...@kernel.org; >dvh...@infradead.org; linux-kernel@vger.kerne

RE: [PATCH] x86: Re-enable IO-APIC for non-SMP X86_32

C and as a >consequence re-enables support for IO-APIC on 32 bit uniprocessor X86 >systems. > >Since Intel CE, Intel MID and Intel Quark are all 32-bit uniprocessor >systems with an IO-APIC re-enabling IO-APIC for 32-bit x86 is required. > >Signed-off-by: Bryan O'Donoghue >

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

>-Original Message- >From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie] >Sent: Thursday, January 29, 2015 11:22 PM >To: Ong, Boon Leong >Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x...@kernel.org; >dvh...@infradead.org; linux-kernel@vger.kernel.org; And

RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000

>On 29/01/15 15:40, Bryan O'Donoghue wrote: >>> It would be nice to have two variants (1) index based & (2) address >>> based. >> >> Understood. The direction from Ingo was to have address based external >> interface imr_del_range() and support an index based internal >> imr_clear() - internally.

RE: [PATCH v7 2/2] x86, quark: Add Intel Quark platform support

h...@infradead.org; andy.shevche...@gmail.com; Ong, Boon Leong; linux- >ker...@vger.kernel.org >Cc: Bryan O'Donoghue >Subject: [PATCH v7 2/2] x86, quark: Add Intel Quark platform support > >Add Intel Quark platform support. Quark needs to pull down all unlocked IMRs to >ensure agreeme

RE: [PATCH v7 1/2] x86: Add Isolated Memory Regions for Quark X1000

2015 11:06 AM >To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org; >dvh...@infradead.org; andy.shevche...@gmail.com; Ong, Boon Leong; linux- >ker...@vger.kernel.org >Cc: Bryan O'Donoghue >Subject: [PATCH v7 1/2] x86: Add Isolated Memory Regions for Quark X100

RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver

>-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Ong, Boon Leong >Sent: Monday, February 23, 2015 9:39 AM >To: Kweh, Hock Leong; Zhang, Rui; edubez...@gmail.com >Cc: linux...@vger.kernel.org; LKML

[PATCH v2 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

rmal_zone0/ For example: - to read DTS temperature $ cat temp - to read critical trip point $ cat trip_point_0_temp - to read trip point type $ cat trip_point_0_type - to emulate temperature raise to test orderly shutdown by Linux distro $ echo 105 > emul_temp Signed-off-by: Ong Boon

[PATCH v2 0/1] Intel Quark X1000 DTS thermal driver

ttyS1. Please kindly review the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v2: * Fix several commit write-up grammar, choice of words. * Ensure "int ret" in correct ord

[PATCHv3 0/1] Intel Quark X1000 DTS thermal driver

dly review the patch at your convenient time and provide me feedback for improvement. Appreciate your time and effort. Thank You Ong Boon Leong Intel Corp. --- Changes in v3: * Kconfig dependency changed to X86_INTEL_QUARK Changes in v2: * Fix several commit write-up grammar, choice of words. * E

[PATCHv3 1/1] thermal: intel Quark SoC X1000 DTS thermal driver

; + + soc_dts = alloc_soc_dts(); + if (IS_ERR(soc_dts)) { + err = PTR_ERR(soc_dts); + goto err_free; + } + + return 0; + +err_free: + free_soc_dts(soc_dts); + return err; +} + +static void __exit intel_quark_thermal_exit(void) +{ + free_soc_dts(soc_

  1   2   >