n which is used as external clock input is selected by using a
custom optional property called "adi,ext-clk-pin". If this field is left
empty, DIO2 is assigned as default external clock input pin.
Signed-off-by: Stefan Popa
---
.../devicetree/bindings/iio/imu/adi,adis16480.txt | 34 +
one function at a time (data ready line
selection or external clock input).
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 186 ++--
1 file changed, 179 insertions(+), 7 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/ii
On Wed, Mar 06, 2019 at 11:10:41AM +0200, Adalbert Lazăr wrote:
> On Wed, 6 Mar 2019 08:41:04 +0000, Stefan Hajnoczi wrote:
> > On Tue, Mar 05, 2019 at 08:01:45PM +0200, Adalbert Lazăr wrote:
> > The pkt argument is the received packet that we must reply to.
> > The reply pac
ier to read like this:
struct virtio_vsock_pkt *reply;
...
-- avoid reusing 'pkt'
v
reply = virtio_transport_alloc_pkt(&info, 0, ...);
if (!reply)
return -ENOMEM;
t = virtio_transport_get_ops();
if (!t) {
virtio_transport_free_pkt(reply); <-- prevent mem
On 06.03.2019 00:39, Robin Murphy wrote:
> Hi Stefan,
>
> On 2019-03-05 10:18 pm, Stefan Agner wrote:
>> The W macro for generating wide instructions when targeting Thumb-2
>> is not required for the preload data instructions (pld, pldw) since
>> they are only availabl
On 05.03.2019 23:21, Nick Desaulniers wrote:
> On Tue, Mar 5, 2019 at 2:17 PM Stefan Agner wrote:
>>
>> The assembler option -mauto-it is no longer a valid option. It has
>> been removed from the documentation in July 2009, which is well
>> before the release date
The assembler option -mauto-it is no longer a valid option. It has
been removed from the documentation in July 2009, which is well
before the release date of the currently supported binutils version
2.20.
Signed-off-by: Stefan Agner
---
arch/arm/Makefile | 3 +--
1 file changed, 1 insertion
]
^
1 error generated.
Drop the macro to make sure non-wide variants of pld and pldw are
emitted in all cases.
Signed-off-by: Stefan Agner
---
arch/arm/include/asm/processor.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/include/asm/processor.h b/arch/
actually work.
>> > So maybe another approach would be to make kexec depend on MMU for
>> > ARM - but I'm afraid I don't really know.
>>
>> Yeah, I've disabled KEXEC in my testing config. All I do care about is
>> to test nommu specific code path
Hi,
since this patch change only one board, the subject could be more specific:
ARM: dts: bcm2835-rpi-b-rev2: Fix hdmi hpd gpio pull
> Helen Koike hat am 4. März 2019 um 22:48
> geschrieben:
>
>
> Raspberry pi board model B revison 2 have the hot plug detector gpio
> active high (and not low
use it doesn't have the proper
format.
Should i take care of this?
Can i add your Signed-off-by including your mail address?
Stefan
>
> Regards,
> Helen
>
> ---
> arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
nu.org/bugzilla/show_bug.cgi?id=88648
Signed-off-by: Stefan Agner
---
I missed this instance in my previous commits and realized only
after running some randconfig.
arch/arm/include/asm/uaccess.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/include/asm/uac
ot;.syntax unified" even in ARM mode. However, the option
is broken since GCC version 6 (see GCC PR88648 [1]). Work
around by adding ".syntax unified" as part of the inline
assembly.
[0]
https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-masm-syntax-unified
[1] https://gcc.gn
gated
> or safe if we are confident all booted cores are safe or
> mitigated.
>
here are the results for Raspberry Pi 3 B:
l1tf:Not affected
meltdown:Not affected
spec_store_bypass:Not affected
spectre_v1:Mitigation: __user pointer sanitization
spectre_v2:Not affected
Tested-by: Stefan Wahren
Document support for ADIS16480 Inertial Measurement Unit.
Signed-off-by: Stefan Popa
Reviewed-by: Rob Herring
---
.../devicetree/bindings/iio/imu/adi,adis16480.txt | 49 ++
MAINTAINERS| 1 +
2 files changed, 50 insertions(+)
create
-documentation/data-sheets/adis16497.pdf
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 97 +
1 file changed, 97 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu/adis16480.c
index c90375d..28cece3 100644
--- a/drivers/iio
When setting the filter frequency, the driver looks into the
adis16480_def_filter_freqs table for the best match. Pass this table to
the chip_info struct since future devices will need to use a different
table.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 13 +
1
.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu/adis16480.c
index 5a2864a..92abc95 100644
--- a/drivers/iio/imu/adis16480.c
+++ b/drivers/iio/imu/adis16480.c
The driver does not have a struct of_device_id table, but supported
devices are registered via Device Trees. This patch adds OF device ID
table.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c
supported devices. However, devices that
will make use of this feature will be added in the future.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu
DIO1 pin as default data ready signal instead of DIO2.
Patch 2:
- nothing changed.
Patch 3, 4:
- give the scale directly in the adis16480_chip_info struct.
Patch 5:
- document the use of DIO1 pin as default data ready signal.
Stefan Popa (7):
iio: imu: adis16480: Add
onfiguration as is, since some devices might be expecting the interrupt
on the wrong physical pin.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 97 -
1 file changed, 95 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c
tively). One would expect that higher
frequency use higher driver strength (and this is the case for i.MX 6).
But with this new/corrected pad values this means we use x4, x2 and x6
for default, 100MHz and 200MHz respectively. This hardly seems right..?
Probably needs fixing too?
--
Stefan
>
] Unhandled fault: imprecise external abort (0x1406) at
0xb6ea7000
...
[ 100.056423] PC is at dw_pcie_read+0x50/0x84
[ 100.060790] LR is at dw_pcie_rd_own_conf+0x44/0x48
...
Signed-off-by: Stefan Agner
---
Changes in v3:
- Rebase on pci/dwc
Changes in v4:
- Rebase on pci/dwc
Changes in v5
On 25.02.2019 17:52, Trent Piepho wrote:
> On Mon, 2019-02-25 at 16:15 +, Leonard Crestez wrote:
>> On Mon, 2019-02-25 at 17:02 +0100, Stefan Agner wrote:
>> > Define the length of the DBI registers and limit config space to its
>> > length. This makes sure that
On 25.02.2019 21:19, Bjorn Helgaas wrote:
> [+cc Thinh]
>
> On Mon, Feb 25, 2019 at 10:52 AM Trent Piepho wrote:
>> On Mon, 2019-02-25 at 16:15 +, Leonard Crestez wrote:
>> > On Mon, 2019-02-25 at 17:02 +0100, Stefan Agner wrote:
>> > > Define the length o
] Unhandled fault: imprecise external abort (0x1406) at
0xb6ea7000
...
[ 100.056423] PC is at dw_pcie_read+0x50/0x84
[ 100.060790] LR is at dw_pcie_rd_own_conf+0x44/0x48
...
Signed-off-by: Stefan Agner
---
Changes in v3:
- Rebase on pci/dwc
Changes in v4:
- Rebase on pci/dwc
Changes in v5
This adds the tachometer interrupt to the pwm-fan binding, which is
necessary for RPM support.
Signed-off-by: Stefan Wahren
---
Documentation/devicetree/bindings/hwmon/pwm-fan.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/hwmon
e atomic_t to avoid races of the pulse counter
- measure sample time to make rpm more reliable under load
- make sysfs entry fan1_input conditional
- add dt-property to define interrupts per fan revolution
- example for fan with RPM support
Stefan Wahren (3):
dt-bindings: hwmon: Add tachometer
This adds a short description for the new RPM support of the pwm-fan
driver.
Signed-off-by: Stefan Wahren
---
Documentation/hwmon/pwm-fan | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/hwmon/pwm-fan b/Documentation/hwmon/pwm-fan
index 18529d2..82fe967 100644
--- a
This adds RPM support to the pwm-fan driver in order to use with
fancontrol/pwmconfig. This feature is intended for fans with a tachometer
output signal, which generate a defined number of pulses per revolution.
Signed-off-by: Stefan Wahren
---
drivers/hwmon/pwm-fan.c | 94
On 25.02.2019 15:47, Leonard Crestez wrote:
> On Mon, 2019-02-25 at 15:25 +0100, Stefan Agner wrote:
>> Define the length of the DBI registers and limit config space to its
>> length. This makes sure that the kernel does not access registers
>> beyond that point, avoiding the
] Unhandled fault: imprecise external abort (0x1406) at
0xb6ea7000
...
[ 100.056423] PC is at dw_pcie_read+0x50/0x84
[ 100.060790] LR is at dw_pcie_rd_own_conf+0x44/0x48
...
Signed-off-by: Stefan Agner
---
Changes in v3:
- Rebase on pci/dwc
Changes in v4:
- Rebase on pci/dwc
Changes in v5
+ soc_dev_attr->family = "Freescale i.MX";
> +
> + root = of_find_node_by_path("/");
> + ret = of_property_read_string(root, "model", &soc_dev_attr->machine);
> + if (ret)
> + goto free_soc;
> +
> + id =
This adds optional regulator support to the pwm-fan driver. This is
necessary for pwm fans which are powered by a switchable supply.
Signed-off-by: Stefan Wahren
---
drivers/hwmon/pwm-fan.c | 43 ++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff
ement more consistent bail out handling
- enable regulator before setup PWM
- make sure we disable regulator if probe fails
Stefan Wahren (2):
dt-bindings: hwmon: Add optional regulator support to pwm-fan
hwmon: pwm-fan: Add optional regulator support
.../devicetree/bindings/hwmon/pwm-fa
This adds an optional regulator support (e.g. switchable supply) to the
pwm fan binding.
Signed-off-by: Stefan Wahren
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/hwmon/pwm-fan.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/hwmon
Document support for ADIS16480 Inertial Measurement Unit.
Signed-off-by: Stefan Popa
---
.../devicetree/bindings/iio/imu/adi,adis16480.txt | 49 ++
MAINTAINERS| 1 +
2 files changed, 50 insertions(+)
create mode 100644 Documentation
supported devices. However, devices that
will make use of this feature will be added in the future.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu
onfiguration as is, since some devices might be expecting the interrupt
on the wrong physical pin.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 97 -
1 file changed, 95 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c
/technical-documentation/data-sheets/adis16495.pdf
Link:
https://www.analog.com/media/en/technical-documentation/data-sheets/adis16497.pdf
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 72 +
1 file changed, 72 insertions(+)
diff --git a
The driver does not have a struct of_device_id table, but supported
devices are registered via Device Trees. This patch adds OF device ID
table.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c
.
Stefan Popa (5):
iio: imu: adis16480: Add support for configurable drdy indicator
iio: imu: adis16480: Add OF device ID table
iio: imu: adis16480: Treat temperature scale in a generic way
iio: imu: adis16480: Add support for ADIS1649x family of devices
iio: imu: adis16480: Add docs for
On Mi, 2019-02-20 at 10:29 +, Jonathan Cameron wrote:
> [External]
>
>
> On Tue, 19 Feb 2019 19:12:14 +0200
> Stefan Popa wrote:
>
> >
> > The FNCTIO_CTRL register provides configuration control for each I/O
> > pin
> > (DIO1, DIO2, DIO3 and DIO
ep_values_up_to_date(struct
> > kone_device *kone,
> > case kone_mouse_event_switch_profile:
> > kone->actual_dpi = kone->profiles[event->value -
> > 1].
> > startup_dpi;
> > + /* fall through */
> >
Document support for ADIS16480 Inertial Measurement Unit.
Signed-off-by: Stefan Popa
---
.../devicetree/bindings/iio/imu/adi,adis16480.txt | 49 ++
MAINTAINERS| 1 +
2 files changed, 50 insertions(+)
create mode 100644 Documentation
supported devices. However, devices that
will make use of this feature will be added in the future.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu
/technical-documentation/data-sheets/adis16495.pdf
Link:
https://www.analog.com/media/en/technical-documentation/data-sheets/adis16497.pdf
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 72 +
1 file changed, 72 insertions(+)
diff --git a
The driver does not have a struct of_device_id table, but supported
devices are registered via Device Trees. This patch adds OF device ID
table.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c
from the devicetree. The
'interrupt-names' property is optional, if it is not specified, then the
factory default DIO2 data ready signal is used.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 76 +
1 file changed, 76 insertion
called.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu/adis16480.c
index a27fe20..d222188 100644
--- a/drivers/iio/imu/adis16480.c
+++ b/drivers/iio
missing docs
Stefan Popa (6):
iio: imu: adis16480: Use the default data ready pin configuration
iio: imu: adis16480: Add support for configurable drdy indicator
iio: imu: adis16480: Add OF device ID table
iio: imu: adis16480: Treat temperature scale in a generic way
iio: imu: adis16480: Add
From: Michael Hennerich
Some devices like the ADIS16460 IMU require a stall period between
transfers. The default value of 10us are not enough. Introduce a per
transfer configurable delay.
Signed-off-by: Michael Hennerich
Signed-off-by: Stefan Popa
---
drivers/spi/spi.c | 3
On 2/15/19 8:49 PM, Pavel Machek wrote:
On Fri 2019-02-15 13:50:10, Stefan Mavrodiev wrote:
Teres-I and A64-OLinuXino commes with populated LED connected
to AXP803. So to be used as battery indication, pass the LED control
to the charger itself in mode 0 ( FULL while charging, OFF no battery
On 2/15/19 8:32 PM, Pavel Machek wrote:
Hi!
On Fri, Feb 15, 2019 at 01:50:06PM +0200, Stefan Mavrodiev wrote:
+static ssize_t control_store(struct device *dev, struct device_attribute *attr,
+const char *buf, size_t size)
+{
+ struct led_classdev *cdev
> -Original Message-
> From: Russell King - ARM Linux admin
> Sent: Monday, February 18, 2019 1:28 PM
> To: Stefan Chulski
> Cc: Antoine Tenart ; da...@davemloft.net;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org;
> thomas.petazz...@bootlin.com; maxime.c
hevall...@bootlin.com;
> gregory.clem...@bootlin.com; miquel.ray...@bootlin.com; Nadav Haklai
> ; Stefan Chulski ; Yan
> Markman ; m...@semihalf.com
> Subject: [EXT] Re: [PATCH net-next 10/13] net: mvpp2: reset the XPCS while
> reconfiguring
g between 10Gbase-KR and SGMII, or
> as will be the case with 2.5G support for the Alaska PHYs, 2500base-X.
Exist one mode that we should add to PPv2&COMPHY 5Gbase-KR(5GBASE-T).
Stefan,
Best Regards.
On 2/15/19 1:50 PM, Stefan Mavrodiev wrote:
Most of AXP20x PMIC chips have built-in battery charger with LED indicator.
The LED can be controlled ether by the charger or manually by a register.
The default is (except for AXP209) manual control, which makes this LED
useless, since there is no
Add dt node for axp20x-led driver controlling CHGLED.
Default status is disabled, since it may be not used.
Signed-off-by: Stefan Mavrodiev
---
arch/arm/boot/dts/axp209.dtsi | 5 +
arch/arm/boot/dts/axp22x.dtsi | 5 +
arch/arm/boot/dts/axp81x.dtsi | 5 +
3 files changed, 15
This adds the devicetree bindings for charge led indicator found
on most of X-Powers AXP20X PMICs.
Signed-off-by: Stefan Mavrodiev
---
.../devicetree/bindings/leds/leds-axp20x.txt | 74 +++
1 file changed, 74 insertions(+)
create mode 100644 Documentation/devicetree/bindings
Teres-I and A64-OLinuXino commes with populated LED connected
to AXP803. So to be used as battery indication, pass the LED control
to the charger itself in mode 0 ( FULL while charging, OFF no battery
or completed).
Signed-off-by: Stefan Mavrodiev
---
arch/arm64/boot/dts/allwinner/sun50i-a64
idden.
Also this binding is enabled only for OLIMEX boards, since I have
no knowlegde if the other manifactures are populating this LED.
Signed-off-by: Stefan Mavrodiev
---
arch/arm/boot/dts/sun7i-a20-olimex-som-evb.dts| 6 ++
arch/arm/boot/dts/sun7i-a20-olimex-som204-evb.dts | 6 ++
driver.
Signed-off-by: Stefan Mavrodiev
---
drivers/leds/Kconfig | 10 ++
drivers/leds/Makefile | 1 +
drivers/leds/leds-axp20x.c | 291 +
3 files changed, 302 insertions(+)
create mode 100644 drivers/leds/leds-axp20x.c
diff --git a/drivers/leds
Add axp20x-led cell for AXP20x, AXP221, AXP223, AXP228, AXP803, AXP809
and AXP813.
Signed-off-by: Stefan Mavrodiev
---
drivers/mfd/axp20x.c | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index 3c97f2c0fdfe
Add dt node for axp20x-led driver controlling CHGLED.
Default status is disabled, since it may be not used.
Signed-off-by: Stefan Mavrodiev
---
arch/arm64/boot/dts/allwinner/axp803.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/axp803.dtsi
b/arch
ff-by: Stefan Mavrodiev
---
arch/arm/boot/dts/sun8i-a33-olinuxino.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a33-olinuxino.dts
b/arch/arm/boot/dts/sun8i-a33-olinuxino.dts
index 3d78169cdeed..a1e36ee51bbb 100644
--- a/arch/arm/boot/dts/sun8i-a33-olinuxino.dts
consumers
Stefan Mavrodiev (8):
leds: Add support for AXP20X CHGLED
mfd: axp20x: Add axp20x-led cell
dt-bindings: leds: Add binding for axp20x-led device driver
arm64: dts: allwinner: axp803: add charge led node
arm64: dts: allwinner: Enable AXP803 CHGLED for Olimex boards
arm: dts: axpxx
patch for another driver. Is there any driver that I
> can
> > > > > fix a style warning?
> > > >
> > > > Maybe, one checkstyle patch is enough, right? Which drivers can I
> truly
> > > > contribute to?
> > >
> > > How about the
> Eric Anholt hat am 13. Februar 2019 um 19:28 geschrieben:
>
>
> Stefan Wahren writes:
>
> > Hi Eric,
> >
> > Am 13.02.19 um 01:33 schrieb Eric Anholt:
> >> The clock driver may probe after ours and so we need to pass the
> >> -EPROBE_DE
dom->clk = devm_clk_get(dev->parent, name);
> + if (IS_ERR(dom->clk)) {
> + int ret = PTR_ERR(dom->clk);
> +
> + if (ret == -EPROBE_DEFER)
> + return ret;
is it safe to proceed in the other error cases?
Even it would be more consistent with clk_prepare_enable() to print an
error here.
> + }
>
>
Thanks
Stefan
unified" as part of the inline
assembly.
[0]
https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-masm-syntax-unified
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88648
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
Changes in v2:
- Force unified syntax for inline assembler
some assembler which the integrated assembler does
not like (yet). But it is a big step towards that direction.
--
Stefan
Stefan Agner (5):
ARM: use unified assembler in macros
ARM: use unified assembler in headers
ARM: use unified assembler in assembly files
ARM: use unified assembler in c fil
Remove the -mno-warn-deprecated assembler flag to make sure the GNU
assembler warns in case non-unified syntax is used.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
Reviewed-by: Nick Desaulniers
---
Changes in v2:
- Remove AFLAGS_NOWARN from CFLAGS_ISA
arch/arm/Makefile | 7 ++-
1
Use unified assembler syntax (UAL) in assembly files. Divided
syntax is considered deprecated. This will also allow to build
the kernel using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
arch/arm/boot/bootp/init.S| 2 +-
arc
Use unified assembler syntax (UAL) in headers. Divided syntax is
considered deprecated. This will also allow to build the kernel
using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
Changes in v2:
- Remove excessive null tokens
- Move t token b
Use unified assembler syntax (UAL) in macros. Divided syntax is
considered deprecated. This will also allow to build the kernel
using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
Changes in v2:
- Remove excessive null tokens
arch/ar
On 10.02.2019 22:24, Nicolas Pitre wrote:
> On Sun, 10 Feb 2019, Stefan Agner wrote:
>
>> This patchset converts all assembly code to unified assembler
>> language (UAL) compatible assembly code. From what I can tell,
>> this mainly boils down to using conditional infixes
On 11.02.2019 19:17, Nick Desaulniers wrote:
> On Sat, Feb 9, 2019 at 9:28 AM Stefan Agner wrote:
>>
>> Thanks for the reviews so far.
>>
>> During some more testing I stumbled upon another issue:
>>
>> On 07.02.2019 10:48, Stefan Agner wrote:
>> &
[adding Mark Brown]
On 11.02.2019 02:23, Shawn Guo wrote:
> On Thu, Feb 07, 2019 at 09:00:44PM +, Trent Piepho wrote:
>> On Mon, 2019-01-07 at 14:22 +0100, Stefan Agner wrote:
>> > Allow to use DMA for SPI by adding the appropriate DMA properites
>> > to the ecspi
On 12.02.2019 12:33, Lorenzo Pieralisi wrote:
> On Tue, Feb 12, 2019 at 09:54:54AM +0100, Lucas Stach wrote:
>> Hi Bjorn,
>>
>> Am Montag, den 11.02.2019, 15:39 -0600 schrieb Bjorn Helgaas:
>> > On Wed, Feb 06, 2019 at 10:57:32AM +0100, Stefan Agner wrote:
>&
Remove the -mno-warn-deprecated assembler flag to make sure the GNU
assembler warns in case non-unified syntax is used.
Signed-off-by: Stefan Agner
---
Changes in v2:
- Remove AFLAGS_NOWARN from CFLAGS_ISA
arch/arm/Makefile | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff
Use unified assembler syntax (UAL) in assembly files. Divided
syntax is considered deprecated. This will also allow to build
the kernel using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
---
arch/arm/boot/bootp/init.S| 2 +-
arch/arm/boot/compressed/ll_char
Use unified assembler syntax (UAL) in inline assembler. Divided
syntax is considered deprecated. This will also allow to build
the kernel using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
---
Changes in v2:
- Force unified syntax for inline assembler using .syntax unified
arc
some assembler which the integrated assembler does
not like (yet). But it is a big step towards that direction.
--
Stefan
Stefan Agner (5):
ARM: use unified assembler in macros
ARM: use unified assembler in headers
ARM: use unified assembler in assembly files
ARM: use unified assembler in c fil
Use unified assembler syntax (UAL) in headers. Divided syntax is
considered deprecated. This will also allow to build the kernel
using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
---
Changes in v2:
- Remove excessive null tokens
- Move t token before conditional token
arc
Use unified assembler syntax (UAL) in macros. Divided syntax is
considered deprecated. This will also allow to build the kernel
using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
---
Changes in v2:
- Remove excessive null tokens
arch/arm/lib/copy_from_user.S | 2 +-
arch/ar
On 07.02.2019 17:10, Nicolas Pitre wrote:
> On Thu, 7 Feb 2019, Stefan Agner wrote:
>
>> Use unified assembler syntax (UAL) in headers. Divided syntax is
>> considered depricated. This will also allow to build the kernel
>> using LLVM's integrated assembler.
>
Thanks for the reviews so far.
During some more testing I stumbled upon another issue:
On 07.02.2019 10:48, Stefan Agner wrote:
> Use unified assembler syntax (UAL) in inline assembler. Divided
> syntax is considered depricated. This will also allow to build
> the kernel using LLVM
On 2/8/19 5:00 PM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 04:21:02PM -0500, Stefan Berger wrote:
I still think that in 5/5 branching could be better but is not a biggie
for me (does not make the implementation as whole any kind of mess) and
since it is now peer tested I rather would not
On 1/18/19 10:00 AM, Jarkko Sakkinen wrote:
On Fri, Jan 11, 2019 at 08:28:00PM +, Safford, David (GE Global Research)
wrote:
You might mention that this is an important feature, as on at least some
systems, ppi function 23 is the only way to enable/disable PCR banks.
I have tested this pat
On 2/8/19 3:46 PM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 03:32:32PM -0500, Stefan Berger wrote:
tpm_del_char_device also needs the start/stop!
Done and updated the commit message to have all the call sites:
* tpm_chip_register()
* tpm_class_shutdown
On 2/8/19 3:23 PM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 02:27:31PM -0500, Stefan Berger wrote:
On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
*/
if (rc > 0) {
dev_warn(&chip->dev,
"%s: send(): invalid value %d\n", __func__, rc);
gt; or safe if we are confident all booted cores are safe or
> mitigated.
>
The whole series is:
Tested-by: Stefan Wahren
with a Raspberry Pi 3 B+
On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
*/
if (rc > 0) {
dev_warn(&chip->dev,
"%s: send(): invalid value %d\n", __func__, rc);
rc = 0;
}
Should be fairly safe play now.
Unfortuantely it isn't. You seemed to have lost the
EXPORT_SYMBOL_GPL(tpm_chip_start/s
completely.
Cc: sta...@vger.kernel.org
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
Let me know when you put it into your tree, I'll give it a spin while I
am at it. :-)
On 2/8/19 11:30 AM, Jarkko Sakkinen wrote:
drivers/char/tpm/st33zp24/st33zp24.c | 2 +-
tpm_ibmvtpm.c needs an update of the description of the send function.
static int i2c_atmel_send(struct tpm_chip *chip, u8 *buf,
size_t len)
if (status < 0)
return status;
+ /* The upper layer does not support incomplete sends. */
+ if (status != len)
+ return -E2BIG;
+
return 0;
}
Reviewed-by: Stefan Berger
On 2/8/19 11:30 AM, Jarkko Sakkinen wrote:
static void tpm_nsc_cancel(struct tpm_chip *chip)
diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c
index 60e2038652b8..1d781c19f112 100644
--- a/drivers/char/tpm/tpm_tis_core.c
+++ b/drivers/char/tpm/tpm_tis_core.c
@@ -507
On 2/8/19 11:07 AM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 10:45:53AM -0500, Stefan Berger wrote:
On 2/8/19 10:42 AM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 09:42:16AM -0500, Stefan Berger wrote: > On 2/8/19 9:05
AM, Jarkko Sakkinen wrote:
At least tpm_nsc_send (tpm_ns
1001 - 1100 of 4529 matches
Mail list logo
