Age | Commit message (Collapse) | Author | Files | Lines |
|
Openbmc/config fixes
|
|
Openbmc/i2c fixes
|
|
Openbmc/dt fixes
|
|
So the core code will enumerate for devices.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
CONFIG_I2C_DEBUG_CORE + systemd-journald = infinite loop
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
We have these listed in the device tree.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
... so we don't lose too much dmesg output. These can be enabled through
dynamic debug anyway.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
We geta bunch of warnings at the moment.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
the dts files for palmetto and barreleye are mostly the same; use a dtsi
file for the common chip parts, keeping only the board-specific things
in the per-platform files.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
They will only be enabled if the status property is changed from
"disabled".
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
We do not support DMA, and have not tested any slave support, however
master mode byte-at-a-time is working.
The device tree currently includes the first and second buses.
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
We need the numbers for exporting anyway.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
We have a set of interrupt registers in each bank; this change
adds a gpio irqchip to hook them up to the GPIO code.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
... nothing uses it.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Rather than having a global bt_host, use references from the
file & miscdev. This removes the restriction on the number of bt-host
devices.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
No need to use a global miscdev here.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
The interface we're using here is specific to the aspeed
hardware implementation.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
We have 'bt' in a few places, 'bt-host' in others. Unify on bt-host.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
.. to avoid any issues with signed vs unsigned types.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
No functional changes.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
We have a bunch of unused functions.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Currently, the watchdog timer does nothing on expiry - the 'SoC system'
reset type doesn't seem to have any effect.
This change uses the 'full chip' reset type instead.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
We do the same reset procedure in apeed_wdt_enable and our reboot
notifier, so move these to a separate function.
Also, use a couple of definitions for the watchdog control value
rather than a hardcoded '3'.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Kernel fixes for openbmc
|
|
It's the only module present.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
Our .dts assumes that the UART clock is divided by 13, but different
u-boots may leave this bit in different states. Initialise it in
aspeed_early_init explicitly.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
|
|
arm/aspeed_defconfig: Add required options to boot with systemd
|
|
|
|
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
This enables IP/UDP/TCP offload checksum according to information
passed on from bootloader through device-tree. The offload doesn't
working properly when the interface works in NCSI mode.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
The NIC has the possibility to connect to NCSI package and channel.
This supports NCSI enabled interface. When the network device is
registered, the accompanying NCSI device is registered. When the
interface is to be brought up, the NCSI device is started to probe
NCSI topology and choose one active channel automatically. On the
other handle, when the interface is to be brought down, the interface
will be shuted down when the NCSI device is teared down.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
The patch replaces variable name "use_nc_si" with "use_ncsi". No
function changed.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
This adds netlink support so that userland can retrieve the NCSI
topology on the specified interface. Also, more netlink commands
are introduced to retrieve information from the active channel
or configure the active channel with provided options.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
There are multiple packages and channels connecting to NCSI enabled
interface. The available packages and channels are probed with NCSI
packets when NCSI device is started. Among the available packages
and channels, only one channel should be selected to be active to
provide service. When the active channel enters to failure state,
we need choose another channel as active one to do failover.
This implements the state machine to support above tasks. Also, the
public interfaces are exposed for NIC driver to manage NCSI device.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
NCSI packet encapsulated in ethernet frame is recognized by the
ethernet protocol field (0x88F8). According to NCSI spec, the
destination MAC field should be 0xFF's, but the source MAC field
could be arbitrary one since channel field in NCSI header indicates
the source of the packet.
There are 3 types of packets depending on the type field in the NCSI
packet header: command, response, Asynchronous Event Notification
(AEN). The command packets are sent from NCSI enabled interace to
the NCSI package or channel for purpose of information retrival or
configuration. The response packets, as responses to the received
command packets, originate from NCSI package or channel and terminate
at NCSI enabled interface. AEN packets are sent from NCSI channel
for asynchronous events that might indicate failure detected on
the active channel.
This implements the functions to handle NCSI packets.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
According to NCSI spec (DSP0222), the NCSI enabled interface can
connected to multiple packages simultaneously, up to 8 packages.
Each package includes multiple channels, up to 32 channels. At
one moment, one channel is enabled to provide service to the NCSI
enabled interface. Besides, each channel comprises capabilities,
modes, filters, version and statistics etc. All of them are
resources to NCSI protocol stack.
At the meanwhile, the NCSI device seen from NIC driver is
represented by "struct ncsi_dev", which is expected to populated
and started by NIC driver before the NIC can work. All possible
NCSI packages and NCSI channels connected to the NCSI interface
are tracked from the NCSI device. Also, the NCSI device recognizes
active channel that is currently providing service to NCSI enabled
interface. Also, the NCSI requests (pairs of command and response)
are embedded in NCSI device.
This introduces the data structs to represents the NCSI resources
mentioned as above. Also, functions used by NCSI stack internally
are implemented. Besides, this introduces kernel config option
CONFIG_NET_NCSI to enable NCSI stack.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
|
|
This patch adds a simple device driver to expose the iBT interface on
Aspeed chips as a character device (/dev/bt).
Signed-off-by: Alistair Popple <alistair@popple.id.au>
|
|
The Aspeed GPIO menu entry was added under "PCI GPIO expanders" which
depends on PCI which may not be enabled for Aspeed. Move the entry to
the "Memory mapped GPIO drivers" which describes the Aspeed GPIO
driver more correctly.
Signed-off-by: Alistair Popple <alistair@popple.id.au>
|
|
Signed-off-by: Joel Stanley <joel@jms.id.au>
|