Introduced a HUB component + front panel IRQ handling
A HUB component was introduced. This HUB component has all the knowledge
about the Yeelight Bedside Lamp 2 hardware. It known what pins are used,
that PWM frequencies to use, what pins to switch in binary mode, etc. etc.
No configuration is required for this HUB component. It's automatically
loaded when the light component is loaded. The light component will use the
HUB component to access the pins that are required for driving the LED
circuitry.
Note that this simplifies the configuration by A LOT. There's no need
anymore to configure the pinouts in the YAML file. This is a logical route
to take, since we're talking about a factory-produced PCB with a soldered on
ESP32 chip, which uses the same GPIO's and settings on all produced devices
(I presume). It would be quite redundant to force every user into
configuring these pinouts themselves.
** Beware to update your device yaml configuration **
There are a few pinouts left to move into the HUB. I will do that in the
next commit. Your device yaml configuration can be simplified along with
these changes. Some of the keys in the existing light configuration block
will no longer work and will have to be removed (red, green, blue, white).
** Further development **
The HUB will be extended make it the central component that also handles
the I2C communication. This way, there is a central place to regulate the
traffic to and from the front panel. We will be able to build upon this
by implementing extra, fully separated components that handle for example
the front panel light level, the power button, the color button and
the slider.
** Interrupt handler for the I2C IRQ trigger pin **
One requirement for the I2C communication has already been implemented: an
interrupt handler for the GPIO that is used by the front panel to signal the
ESP that a new touch or release event is avilable to be read.
It doens't do anything functionally right now, but if you watch the log
file, you will see that touch events are detected and that they trigger some
log messages.
3 years ago |
|
- #pragma once
-
- #include "common.h"
- #include "esphome/core/component.h"
- #include "esphome/core/esphal.h"
- #include "esphome/components/ledc/ledc_output.h"
-
- namespace esphome {
- namespace yeelight {
- namespace bs2 {
-
- struct TriggerPinStore {
- volatile int queue_length = 0;
- static void isr(TriggerPinStore *store);
- };
-
- /**
- * This ISR is used to handle IRQ triggers from the front panel.
- *
- * The front panel pulls the trigger pin low when a new event
- * is available. All we do here to handle the interrupt, is
- * increment a simple queue length counter. Reading the event
- * from the I2C bus will be handled in the main loop, based
- * on this counter.
- */
- void ICACHE_RAM_ATTR HOT TriggerPinStore::isr(TriggerPinStore *store) {
- store->queue_length++;
- }
-
- class YeelightBS2Hub : public Component {
- public:
- // Pins that are used for the RGBWW light.
- ledc::LEDCOutput *red;
- ledc::LEDCOutput *green;
- ledc::LEDCOutput *blue;
- ledc::LEDCOutput *white;
-
- void set_trigger_pin(GPIOPin *pin) { i2c_trigger_pin_ = pin; }
- void set_red_pin(ledc::LEDCOutput *pin) { red = pin; }
- void set_green_pin(ledc::LEDCOutput *pin) { green = pin; }
- void set_blue_pin(ledc::LEDCOutput *pin) { blue = pin; }
- void set_white_pin(ledc::LEDCOutput *pin) { white = pin; }
-
- void setup() {
- ESP_LOGCONFIG(TAG, "Setting up I2C trigger pin interrupt...");
- this->i2c_trigger_pin_->setup();
- this->i2c_trigger_pin_->attach_interrupt(
- TriggerPinStore::isr, &this->trigger_pin_store_, FALLING);
- }
-
- void dump_config() {
- ESP_LOGCONFIG(TAG, "I2C");
- LOG_PIN(" Interrupt pin: ", this->i2c_trigger_pin_);
- }
-
- void loop() {
- if (this->trigger_pin_store_.queue_length > 0) {
- this->counter_++;
- ESP_LOGD(TAG, "Front Panel interrupt queue=%d, counter=%d",
- this->trigger_pin_store_.queue_length, this->counter_);
- this->trigger_pin_store_.queue_length--;
- }
- }
-
- protected:
- // Pin that is used by the front panel to notify the ESP that
- // a touch/release event can be read using I2C.
- GPIOPin *i2c_trigger_pin_;
-
- // Fields that are used for trigger pin interrupt handling.
- int counter_ = 0;
- TriggerPinStore trigger_pin_store_{};
- };
-
- } // namespace bs2
- } // namespace yeelight
- } // namespace esphome
|