Hi Rob,
On Tue, 2019-08-27 at 10:56 -0500, Rob Herring wrote:
> On Tue, Aug 13, 2019 at 11:37:59AM +0100, André Draszik wrote:
> > The i.MX7D variant of the IP can use either an external
> > crystal oscillator input or an internal clock input as
> > a reference clock i
add / enable TI's WiLink8 WLAN module on SDIO2.
Notes:
* power is always enabled (because of bluetooth)
* the downstream delay of 70ms after power-on
doesn't seem to reliably work, hence it was
bumped to 700ms
Signed-off-by: André Draszik
Cc: Ilya Ledvich
Cc: Igor Grinberg
Cc: Rob Herring
add/enable RTC support using the on-board EM3027 real time
clock on i2c2.
Signed-off-by: André Draszik
Cc: Ilya Ledvich
Cc: Igor Grinberg
Cc: Rob Herring
Cc: Mark Rutland
Cc: Shawn Guo
Cc: Sascha Hauer
Cc: Pengutronix Kernel Team
Cc: Fabio Estevam
Cc: NXP Linux Team
Cc: devicet
add / enable TI's WiLink8 Bluetooth module on UART3.
Signed-off-by: André Draszik
Cc: Ilya Ledvich
Cc: Igor Grinberg
Cc: Rob Herring
Cc: Mark Rutland
Cc: Shawn Guo
Cc: Sascha Hauer
Cc: Pengutronix Kernel Team
Cc: Fabio Estevam
Cc: NXP Linux Team
Cc: devicet...@vger.kernel.org
Cc: linux
While not strictly needed as "ethernet-phy-ieee802.3-c22"
is assumed by default if not given explicitly, having
the compatible string here makes it more clear what
this is and which driver handles this - an Ethernet
phy attached to mdio, handled by of_mdio.c
Signed-off-by: André Draszik
, and disable them otherwise.
Also, remove comments which don't add anything that can't be
seen by looking at the code.
Signed-off-by: André Draszik
CC: Andrew Lunn
CC: Florian Fainelli
CC: Heiner Kallweit
CC: "David S. Miller"
CC: net...@vger.kernel.org
---
v2: also remove braces around si
Hi,
On Fri, 2019-08-09 at 14:09 +0300, Vladimir Oltean wrote:
> Hi Andre,
>
> On Fri, 9 Aug 2019 at 13:00, André Draszik wrote:
> > Hi Vladimir,
> >
> > On Fri, 2019-08-09 at 12:43 +0300, Vladimir Oltean wrote:
> > > Hi Andre,
> > >
> >
Hi Vladimir,
On Fri, 2019-08-09 at 12:43 +0300, Vladimir Oltean wrote:
> Hi Andre,
>
> On Fri, 9 Aug 2019 at 03:58, André Draszik wrote:
> > This driver does a funny dance disabling and re-enabling
> > RX and/or TX delays. In any of the RGMII-ID modes, it first
> >
, and disable them otherwise.
Also, remove comments which don't add anything that can't be
seen by looking at the code.
Signed-off-by: André Draszik
CC: Andrew Lunn
CC: Florian Fainelli
CC: Heiner Kallweit
CC: "David S. Miller"
CC: net...@vger.kernel.org
---
drivers/net/phy/at8
Thank you Ted,
On Wed, 2018-01-17 at 13:05 -0500, Theodore Ts'o wrote:
> On Wed, Jan 17, 2018 at 02:38:59PM +0000, André Draszik wrote:
> > > > [...]
> > >
> > > Please be very clear about exactly what security properties are
> > > achieved
> > >
Thank you Ted,
On Wed, 2018-01-17 at 13:05 -0500, Theodore Ts'o wrote:
> On Wed, Jan 17, 2018 at 02:38:59PM +0000, André Draszik wrote:
> > > > [...]
> > >
> > > Please be very clear about exactly what security properties are
> > > achieved
> > >
ptionally benefitting from the TPM's capability to only
unseal kmk.blob when the system is in the expected state,
thereby also protecting fscrypt.blob):
keyctl add trusted kmk "load $(cat /keys/kmk.blob)" @u
keyctl add encrypted fscrypt:1234567890123456 "load $(cat
/keys/fscrypt.b
ptionally benefitting from the TPM's capability to only
unseal kmk.blob when the system is in the expected state,
thereby also protecting fscrypt.blob):
keyctl add trusted kmk "load $(cat /keys/kmk.blob)" @u
keyctl add encrypted fscrypt:1234567890123456 "load $(cat
/keys/fscrypt.bl
Hi Eric,
On Wed, 2018-01-10 at 20:48 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:18PM +0000, André Draszik wrote:
> > diff --git a/Documentation/security/keys/fscrypt.rst
> > b/Documentation/security/keys/fscrypt.rst
> > new file mode 10
Hi Eric,
On Wed, 2018-01-10 at 20:48 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:18PM +0000, André Draszik wrote:
> > diff --git a/Documentation/security/keys/fscrypt.rst
> > b/Documentation/security/keys/fscrypt.rst
> > new file mode 10
Thanks Eric for the review!
On Wed, 2018-01-10 at 20:00 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:16PM +0000, André Draszik wrote:
> > This is heavily based on commit 79a73d188726
> > ("encrypted-keys: add ecryptfs format support"
Thanks Eric for the review!
On Wed, 2018-01-10 at 20:00 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:16PM +0000, André Draszik wrote:
> > This is heavily based on commit 79a73d188726
> > ("encrypted-keys: add ecryptfs format support"
Signed-off-by: André Draszik <g...@andred.net>
Cc: "Theodore Y. Ts'o" <ty...@mit.edu>
Cc: Jaegeuk Kim <jaeg...@kernel.org>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: linux-fscr...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Eric Biggers <ebigg...@goog
Signed-off-by: André Draszik
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: Jonathan Corbet
Cc: linux-fscr...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Eric Biggers
Cc: linux-...@vger.kernel.org
---
Documentation/filesystems/fscrypt.rst | 56 +++--
We now try to acquire the key according to the
encryption policy from both key types, 'logon'
as well as 'encrypted'.
Signed-off-by: André Draszik <g...@andred.net>
Cc: "Theodore Y. Ts'o" <ty...@mit.edu>
Cc: Jaegeuk Kim <jaeg...@kernel.org>
Cc: linux-fscr...@vger
We now try to acquire the key according to the
encryption policy from both key types, 'logon'
as well as 'encrypted'.
Signed-off-by: André Draszik
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: linux-fscr...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Eric Biggers
---
cha
This does the necessary cleanup on driver unload automatically.
Signed-off-by: André Draszik <g...@andred.net>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
Cc: Wim Van Sebroeck <w...@iguana.be>
Cc: Guenter Roeck <li...@roeck-us.net>
Cc: linux-watch...@vger.kernel
This does the necessary cleanup on driver unload automatically.
Signed-off-by: André Draszik
Reviewed-by: Guenter Roeck
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Cc: John Crispin
---
Changes in v2:
- add reviewed-by
---
drivers/watchdog/mt7621_wdt.c | 13
for exactly
that use-case.
Given the watchdog driver core doesn't know what timeout was
originally set by whoever started the watchdog (boot loader),
we make sure to update the timeout in the hardware according
to what the watchdog core thinks it is.
Signed-off-by: André Draszik <g...@andred.net>
C
for exactly
that use-case.
Given the watchdog driver core doesn't know what timeout was
originally set by whoever started the watchdog (boot loader),
we make sure to update the timeout in the hardware according
to what the watchdog core thinks it is.
Signed-off-by: André Draszik
Cc: Wim Van Sebroeck
Cc
Signed-off-by: André Draszik <g...@andred.net>
Cc: Mimi Zohar <zo...@linux.vnet.ibm.com>
Cc: David Howells <dhowe...@redhat.com>
Cc: James Morris <james.l.mor...@oracle.com>
Cc: "Serge E. Hallyn" <se...@hallyn.com>
Cc: "Theodore Y. Ts'o" <t
Signed-off-by: André Draszik
Cc: Mimi Zohar
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: Jonathan Corbet
Cc: Kees Cook
Cc: linux-integr...@vger.kernel.org
Cc: keyri...@vger.kernel.org
Cc: linux-security-mod..
We now try to acquire the key according to the
encryption policy from both key types, 'logon'
as well as 'encrypted'.
Signed-off-by: André Draszik <g...@andred.net>
Cc: Mimi Zohar <zo...@linux.vnet.ibm.com>
Cc: David Howells <dhowe...@redhat.com>
Cc: James Morris <james.l.
We now try to acquire the key according to the
encryption policy from both key types, 'logon'
as well as 'encrypted'.
Signed-off-by: André Draszik
Cc: Mimi Zohar
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: Kees Co
ypted keys with the fscrypt
subsystem can be found in the file 'Documentation/security/keys/fscrypt.rst'.
Signed-off-by: André Draszik <g...@andred.net>
Cc: Mimi Zohar <zo...@linux.vnet.ibm.com>
Cc: David Howells <dhowe...@redhat.com>
Cc: James Morris <james.l.mor...@oracle.com>
Cc: "
ypted keys with the fscrypt
subsystem can be found in the file 'Documentation/security/keys/fscrypt.rst'.
Signed-off-by: André Draszik
Cc: Mimi Zohar
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: Kees Cook
Cc: linux-integ
This does the necessary cleanup on driver unload automatically.
Signed-off-by: André Draszik <g...@andred.net>
Cc: Wim Van Sebroeck <w...@iguana.be>
Cc: Guenter Roeck <li...@roeck-us.net>
Cc: linux-watch...@vger.kernel.org
Cc: John Crispin <j...@phrozen.org>
---
drive
This does the necessary cleanup on driver unload automatically.
Signed-off-by: André Draszik
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Cc: John Crispin
---
drivers/watchdog/mt7621_wdt.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff
timeout was
originally set by whoever started the watchdog (boot loader),
we make sure to update the timeout in the hardware according
to what the watchdog core thinks it is.
Signed-off-by: André Draszik <g...@andred.net>
Cc: Wim Van Sebroeck <w...@iguana.be>
Cc: Guenter Roeck <li.
timeout was
originally set by whoever started the watchdog (boot loader),
we make sure to update the timeout in the hardware according
to what the watchdog core thinks it is.
Signed-off-by: André Draszik
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Cc: John Crispin
) p &'verifier.c'::log_buf
$4 = (char **) 0x8120fe40
(gdb) p &'printk.c'::log_buf
$5 = (char **) 0x8048b7d0
By being explicit about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: André
) p &'verifier.c'::log_buf
$4 = (char **) 0x8120fe40
(gdb) p &'printk.c'::log_buf
$5 = (char **) 0x8048b7d0
By being explicit about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: André D
) p &'verifier.c'::log_buf
$4 = (char **) 0x8120fe40
(gdb) p &'printk.c'::log_buf
$5 = (char **) 0x8048b7d0
By being explicit about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: André
) p &'verifier.c'::log_buf
$4 = (char **) 0x8120fe40
(gdb) p &'printk.c'::log_buf
$5 = (char **) 0x8048b7d0
By being explicit about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: Andr
we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: André Draszik <g...@andred.net>
---
scripts/gdb/linux/dmesg.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/gdb/linux/dmesg.py b/
we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: André Draszik
---
scripts/gdb/linux/dmesg.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/gdb/linux/dmesg.py b/scripts/gdb/linux/d
They're all referenced as utif in the datasheet, not util.
Fixes: 53263a1c6852 ("MIPS: ralink: add mt7628an support")
Fixes: 2b436a351803 ("MIPS: ralink: add MT7628 EPHY LEDs pinmux support")
Signed-off-by: André Draszik <g...@andred.net>
---
arch/mips/ralink/mt7620.c
They're all referenced as utif in the datasheet, not util.
Fixes: 53263a1c6852 ("MIPS: ralink: add mt7628an support")
Fixes: 2b436a351803 ("MIPS: ralink: add MT7628 EPHY LEDs pinmux support")
Signed-off-by: André Draszik
---
arch/mips/ralink/mt7620.c | 18 +
43 matches
Mail list logo
